aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-08-15Snap for 5803298 from df238b4e41d29aa02988d6d8da8ed8e531a7a79f to qt-aml-releaseandroid-mainline-10.0.0_r2android10-mainline-a-releaseandroid-build-team Robot
Change-Id: I883c94b2251bf7e1deb349df5adf4d9954b0df14
2019-07-29Select all .pem and .avbpubkey in otatoolsBaligh Uddin
Apex payload dev keys are stored as .pem files. Apex payload also utilizes .avbpubkey as public keys. Change-Id: I65ced74be02008b666d7bb608f0d0a3ef3769c9c BUG: 138623265
2019-07-17Merge "Disable apex update for GSI" into qt-devTreeHugger Robot
2019-07-15Update auto-gen test config template with EXTRA_CONFIGS placeholderDan Shi
Bug: 134509111 Bug: 136633978 Test: add "require_root: true" to init_benchmarks and libpower_test build the modules, confirm the extra target preparer is added in the test config. Change-Id: I2fdae79d45fd1e5866ee94d1f0e59df106be2a87 Merged-In: I2fdae79d45fd1e5866ee94d1f0e59df106be2a87
2019-07-12Merge "Add Mainline Test Suite (MTS) to build." into qt-devChen Zhu
2019-07-12Merge "Update Security String to 2019-09-05 Bug: 137199979" into qt-devTreeHugger Robot
2019-07-11Merge "releasetools: Ignore nonexistent APEX overrides." into qt-devTreeHugger Robot
2019-07-11Update Security String to 2019-09-05Elisa Pascual Trevino
Bug: 137199979
2019-07-11Update Security String to 2019-09-01Elisa Pascual Trevino
Bug: 137199979
2019-07-11releasetools: Ignore nonexistent APEX overrides.Tao Bao
This allows sharing the same signing config on different target_files zips. Nonexistent APEX will be ignored with a warning. Bug: 137249701 Test: Run sign_target_files_apks with APEX overrides. Change-Id: I2bad0f5c00753ed36ec5ae3431c7dc2ff1fc3e9c
2019-07-09temporarily disable vendor file check for mainlineColin Cross
We want to use prebuilts for apex modules for qt-dev, but it is running afoul of the vendor file check. Disable the check for now until we figure out a better solution. Using Merged-In instead of DNM Bug: 137033385 Test: Forrest run build_test Change-Id: I9db5cb227780ede6aaff0070cd2fd59e95e635e6 Merged-In: 874b7a7766a569613dcd3ae526eaa6e1d4b78866 Merged-In: I99431a9a342e9b0617510e250597f3024ef39322
2019-07-09Snap for 5713174 from 25065c44ccce11172ad769f9f7b52aa3938109cb to qt-aml-releaseandroid-mainline-10.0.0_r3android-mainline-10.0.0_r1android10-mainline-releaseandroid-build-team Robot
Change-Id: I50e4383a10278fd78dd39dd919857298db48545b
2019-07-06Snap for 5709920 from 9547929af43eeb48e4f766daeb822d8d89416691 to qt-aml-releaseandroid-build-team Robot
Change-Id: I83dccd626625428fd9f92c3ad0254cc1d9e9918f
2019-07-05Do not allow building product_services imageJustin Yun
product_services partition is designed for the test purpose only. It must not be included in the target devices. Bug: 134359158 Test: Build configuration for product_services partition must return error message. Change-Id: I6f8cdf73d18ad3174c7b31edb5d5ee10df75a776
2019-07-03Add default LMK properties to GSISzuWei Lin
These LMK properties are product properties. The configuration will be absent when GSI is installed as GSI doesn't mount the product partition. Without these settings, some CTS test cases could fail due to an aggressive LMK. The patch puts these properties in GSI as default values. Bug: 136212765 Bug: 134460917 Test: `run cts -m CtsFileSystemTestCases`, all pass Change-Id: I6fde8db51debcb9bb269aece3a3e4c7e5bb991f6
2019-06-29Snap for 5698743 from d8d0821252e6efec16d3177c7b309df72460dd67 to qt-aml-releaseandroid-build-team Robot
Change-Id: I7d8103b513bca4f31b8f8da2f81747cea54a38e0
2019-06-27Remove lmk.log_stats sysprop from mainline_systemAnton Hansson
It is now set on the /product partition by relevant devices. Bug: 135569569 Test: lunch mainline_system_arm64; inspect system/etc/prop.default Test: boot crosshatch and check the sysprop is still true via "adb shell getprop" Change-Id: I34696977f584a65741c6002e6688d86e66a1f121 Merged-In: I34696977f584a65741c6002e6688d86e66a1f121
2019-06-26Snap for 5688406 from e40cc936ff46d36e8d9800325d9a2002e1e0f8b9 to qt-aml-releaseandroid-build-team Robot
Change-Id: I13bb3e426c1201de8c2b5b29022e1fa51865ede6
2019-06-21Disable apex update for GSIIsaac Chen
Currently, GSI does not include apex support and TARGET_FLATTEN_APEX is true. This will cause issues for vendors with apex support (e.g. Cuttlefish). This change set ro.apex.updatable to false in product to override that sets in vendor. Bug: 135411972 Bug: 134673003 Test: $ lunch aosp_x86-userdebug; m -j; emulator $ lunch aosp_cf_x86_phone-userdebug # Replace system.img in super.img with GSI # The resulted CF could boot and browse the web successfully. Change-Id: I08fd7a1b254aac276926329e064c35b714764936 Merged-In: I08fd7a1b254aac276926329e064c35b714764936 (cherry picked from commit fae280264e64f88057cdaf530fc94bcbceb48fe1)
2019-06-21Enforce property split in GSISzuWei Lin
Pure GSI build targets has no vendor partition, such as aosp_$arch_ab and gsi_$arch. The system properties defined by PRODUCT_PROPERTY_OVERRIDES will be in /system/build.prop. The patch defined a fake BOARD_VENDORIMAGE_FILE_SYSTEM_TYPE to let these system properties flow to vendor and won't pollute the system.img. The bug also move some properties to /product/build.prop. Bug: 135508595 Bug: 131162245 Bug: 134781120 Test: check the /system/build.prop do not have "ro.carrier=unknown" Test: adb remount on GSI Q on P Change-Id: Ib200d66cf98fea572c26338e058bce29eb5e0cd7 Merged-In: Ib200d66cf98fea572c26338e058bce29eb5e0cd7 (cherry picked from commit 711d696eb3af759c63c416b0224faeac1f6c04f1)
2019-06-19Add Mainline Test Suite (MTS) to build.Chen Zhu
Test: m mts Bug: 126277867 Bug: 123411735 Change-Id: Iba6bf89bd4457ed0f5c1eb3351bf5ffd6720441d
2019-06-18Snap for 5667769 from 0c355124bf6681d51a93d32a56519c1e3560b503 to qt-aml-releaseandroid-build-team Robot
Change-Id: If5047deabff492d06b2d3882a0b2c76fcb0590fc
2019-06-17Merge cherrypicks of [8037192] into qt-aml-releaseandroid-build-team Robot
Change-Id: I098c2e3d45b76fd74b24c8fd82cd622bdb2d4b5d
2019-06-17Revert "Update Security String from 08-05 to 2019-08-01 Bug:126590667"Adam Seaton
This reverts commit ef7c2c79154126902194b1bb6bf166b7e201bc83. Reason for revert: Resolve string downgrade issue Change-Id: I28831f2592bba09907b76c7d5ac46326a9c1e9f8 (cherry picked from commit 0c355124bf6681d51a93d32a56519c1e3560b503)
2019-06-17Revert "Update Security String from 08-05 to 2019-08-01 Bug:126590667"Adam Seaton
This reverts commit ef7c2c79154126902194b1bb6bf166b7e201bc83. Reason for revert: Resolve string downgrade issue Change-Id: I28831f2592bba09907b76c7d5ac46326a9c1e9f8
2019-06-15Snap for 5663823 from ef7c2c79154126902194b1bb6bf166b7e201bc83 to qt-aml-releaseandroid-build-team Robot
Change-Id: I02b3f2de8dc190e4e8c4977a5228fed409d0bd30
2019-06-14Update Security String from 08-05 to 2019-08-01 Bug:126590667Paul Scovanner
am: ead61ed19e Change-Id: Iaf434bf5690c3c50371bb11266d300ab7d335184
2019-06-13Snap for 5656554 from 3a25bc8b55a77fbde688e54e8c3785f00d0f0a5d to qt-aml-releaseandroid-build-team Robot
Change-Id: Id9884e29546067ba631db86ff1a2d70c5cf9fb14
2019-06-12Update Security String to 2019-08-05 Bug:126590667Paul Scovanner
am: a3e1c57a95 Change-Id: I0b10bab75834759c3bd216fc77c38c84b445c4e2
2019-06-12Update Security String from 08-05 to 2019-08-01Paul Scovanner
Bug:126590667
2019-06-11Snap for 5651803 from 6d98e835610c0a9fc33bef1f3245fca9ab880dcb to qt-aml-releaseandroid-build-team Robot
Change-Id: Ie27c07a29bbc71881b3870b1846b502b865722f5
2019-06-11Update Security String to 2019-08-05Paul Scovanner
Bug:126590667
2019-06-11Merge "Enabled traced on Android Go devices by default." into qt-devTim Joines
2019-06-08Snap for 5645017 from 97a6690a230bfff7501dc032a8853b41a9f534f0 to qt-aml-releaseandroid-build-team Robot
Change-Id: I43cdbe5ae6bdb49f754c8d483e6517a80df0031b
2019-06-07Enabled traced on Android Go devices by default.Tim Joines
Memory impact of this change: ~1.5MB idle PSS. Test: build low_ram enabled target Bug: 123542916 Change-Id: I5afec17cd0b60cab9c6f336df8a09d3861473394
2019-06-07Snap for 5640946 from c609f1ebb764d627f959c7cefb6071f043963449 to qt-aml-releaseandroid-build-team Robot
Change-Id: I282cd21015e6f529905797cc1a9ed646cdae7f91
2019-06-07Snap for 5637977 from d1447629d940efdc0ca84ea935d8e36b7f9187f0 to qt-aml-releaseandroid-build-team Robot
Change-Id: I108605e2e39c9b06cea05ac9afc82e2233b3f7aa
2019-06-07Snap for 5634188 from 5f27d3c1007b02de45eb50306aee9622e57967aa to qt-aml-releaseandroid-build-team Robot
Change-Id: I91e2f9399625021ad31c166716819917ce598477
2019-06-07Snap for 5633424 from cadeadf764a1ccf44a407e1a1e6948d803331cf3 to qt-aml-releaseandroid-build-team Robot
Change-Id: I6b9c06c18c283ac31cebe6aabc37a8f0a9240bcf
2019-06-07Snap for 5631779 from f0d815f17670d3facd1a6cc31e069326731e4f88 to qt-aml-releaseandroid-build-team Robot
Change-Id: I31e931dc3f36f1ceb770005952339a1b4b70eec9
2019-06-07Snap for 5627994 from 8a8881fac8658c4a3674842899bd451c725b9770 to qt-aml-releaseandroid-build-team Robot
Change-Id: I6fa3d3b8865fe93ed20bae4949511e684faa7874
2019-06-07Snap for 5626917 from 6e387b85ed487fdcb8dccdf4bb16916bc5179fea to qt-aml-releaseandroid-build-team Robot
Change-Id: Id07c6eccb9ccd1cb92ec38edfd55b3bafc961592
2019-06-07Snap for 5623629 from 287a102868c1a02d1248f1e75e557fa6214e49d5 to qt-aml-releaseandroid-build-team Robot
Change-Id: I9d3bb9ccad68ee1a85f59cb402c04118a81b4dae
2019-06-07Snap for 5621407 from 997eb1fc760b1c75c6b4fc2c3a069c64aadf1388 to qt-aml-releaseandroid-build-team Robot
Change-Id: Idfaf79627190402b649f2fc037243b19eecee23b
2019-06-07Snap for 5619620 from 5a6501cdb202b103ba675d3b45730c74fd8c3471 to qt-aml-releaseandroid-build-team Robot
Change-Id: I39cb8fdab35698b001484e2e6384ab16bce6d45c
2019-06-07Version bump to QP1A.190606.002 [core/build_id.mk]android-build-team Robot
Change-Id: I95b0758241cc0f8b5ef09b8d2aaeabc1803fb553
2019-06-06Make change and version bump to QP1A.190606.001android-build-team Robot
Change-Id: Icac4a2d2978fc5941c4c5e0c4874ea59d635be1a
2019-06-05Rebuild recovery-from-boot patch when calling add_img_to_target_files.Tao Bao
When using Verified Boot 2.0, releasetools specifies a salt value based on build fingerprint, so that to give idempotent images. However, the change that removed static `ro.build.fingerprint` [1] broke the behavior, as common.LoadInfoDict still relies on fingerprints. Without a fixed salt, the first call to make_recovery_patch.py and the second one (which writes IMAGES/{boot,recovery}.img) will see different images, which leads to install-recovery.sh failure. Note that currently there's a dependency that requires getting bootable images through two separate calls. make_recovery_patch.py has to happen first to get (placeholder) files in the system image. We then generate canned fs_config files, and finally use add_img_to_target_files.py to write the images. This CL adds a quick workaround to force rebuilding the recovery-from-boot patch while calling add_img_to_target_files.py. [1] https://android-review.googlesource.com/c/platform/build/+/892933 Bug: 134123803 Bug: 134525174 Test: TreeHugger Test: Build a non-A/B target that uses AVB. Run validate_target_files.py on the generated target_files.zip. Change-Id: I5859e30be63bfd54398cf41fd2d907f15285f560 Merged-In: I5859e30be63bfd54398cf41fd2d907f15285f560 (cherry picked from commit 4978fa99d17de70b09472a4c41c8fe610364fbbb)
2019-06-05Snap for 5617038 from 711d58a3df6731636190c21e230b0d2bea360281 to qt-aml-releaseandroid-build-team Robot
Change-Id: I91e722cb5151e230658e7d0e6fe88a9140a8c722
2019-06-05Make change and version bump to QP1A.190605.001android-build-team Robot
Change-Id: I6b7d95613f136840aafb9b1ef137734fa1af2e67
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-03 19:40:14 +0000