Avoid envsetup.sh, which is configuring the environment in a
way that breaks builds on the build servers. This exposes an
issue with the AIDL freeze that was lost in the meantime.
Bug: 234734342
Test: (run script, there is an audio failure)
Change-Id: Ic2888fb316d295a06f465f33d3a6f348a65c30a5
Because bpmodify is safe in multi-process env.
Bug: 190577319
Bug: 229413853
Test: aidl-freeze-api
Change-Id: Ie47afc25e2259bbcbbff50f98fa9d36887558d27
bpmodify isn't safe for multi processes env because it doesn't use any
lock mechanism even with -w option(in-place change)
So, added -j1 option as a temp solution.
Bug: 190577319
Bug: 229413853
Test: run aidl-freeze-api with -j1
Change-Id: I7fabfa1224ea0bb8d71538f4c8012255df28a3e8
When the freeze adds new libraries to the VNDK, we also need to
update the VNDK script.
Bug: 190577319
Test: run script on internal branch
Change-Id: I6f0ab177df5027ced0c4e198bb8a908da088eb85
To put in CI. At the end of every Android release, we need
to do 100,000 things to get the release ready. The process
to finalize the release for AIDL interfaces is automated now,
so we're adding a generic script. The goal is:
1. gradually add more pieces of the finalization process
which can be automated (VNDK, SDK, etc...)
2. when problems happen, we can fix them in real time in CI
3. once the entire release process is in CI, we can optimize
it, and we can require that new requirements on the
Android release process come with a script to satisfy them.
Until then, this script will be used to test the automated parts
of the release process in CI.
Bug: 190577319
Bug: 228979367
Test: ./build/make/finalize_branch_for_release.sh (in the T release branch)
Change-Id: Ie9ff42dd4c6e86d395bde3f14788029e5bde5fb2
