f7a5e2fa4b
- actually do the first step instead of just logging a message, - make sure extension SDK bump gets picked up by the topic, - fix the resources_sdk_int in first step, and unfix in the second. Bug: 278246368 Fixes: 278246368 Test: local run Change-Id: I0d0f4e2ec7f0b584b9fc14a545cfec73a9fcbdea
Finalization tools
This folder contains automation and CI scripts for finalizing Android before release.
Automation:
- Environment setup. Set values for varios finalization constants.
- Finalize SDK. Prepare the branch for SDK release. SDK contains Android Java APIs and other stable APIs. Commonly referred as a 1st step.
- Finalize Android. Mark branch as "REL", i.e. prepares for Android release. Any signed build containing these changes will be considered an official Android Release. Referred as a 2nd finalization step.
- Finalize SDK and submit. Do Finalize SDK step, create CLs, organize them into topic and send to Gerrit. a. Update SDK and submit. Same as above, but updates the existings CLs.
- Finalize Android and submit. Do Finalize Android step, create CLs, organize them into topic and send to Gerrit. a. Update Android and submit. Same as above, but updates the existings CLs.
CI:
Performed in build targets in Finalization branches.
- Finalization Step 1 for Main, git_main-fina-1-release. Test 1st step/Finalize SDK.
- Finalization Step 1 for UDC, git_udc-fina-1-release. Same but for udc-dev.
- Finalization Step 2 for Main, git_main-fina-2-release. Test 1st step/Finalize SDK and 2nd step/Finalize Android. Use local finalization to build and copy presubmits.
- Finalization Step 2 for UDC, git_udc-fina-2-release. Same but for udc-dev.
- Local finalization steps are done only during local testing or in the CI lab. Normally these steps use artifacts from other builds.
Utility:
Full cleanup. Remove all local changes and switch each project into head-less state. This is the best state to sync/rebase/finalize the branch.