7fc38029ec
Run vintf finalization if the target configuration does not set RELEASE_BOARD_API_LEVEL_FROZEN to 'true'; and FINAL_BOARD_API_LEVEL which is the version to finalize is the same with the RELEASE_BOARD_API_LEVEL which is the version that the current tree is building. Also define build-step-0-and-m.sh that runs a test build after the vintf finalization process. Ignore-AOSP-First: finalization script is an exception Bug: 331696132 Test: tools/finalization/build-step-0-and-m.sh Change-Id: I22b9096d57c935e64c4d28f16b95afaa84b79465
Finalization tools
This folder contains automation and CI scripts for finalizing Android before release.
Automation:
- Environment setup. Set values for varios finalization constants.
- Finalize VINTF. Prepare the branch for VINTF release.
- 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 VINTF and submit. Do Finalize VINTF step, create CLs, organize them into topic and send to Gerrit.
- Finalize SDK and submit. Do Finalize SDK step, create CLs, organize them into topic and send to Gerrit.
- Finalize Android and submit. Do Finalize Android step, create CLs, organize them into topic and send to Gerrit.
CI:
Performed in build targets in Finalization branches.
- Finalization Step 0, git_main-fina-0-release. Test Finalize VINTF.
- Finalization Step 1, git_main-fina-1-release. Test Finalize VINTF, Finalize SDK.
- Finalization Step 2, git_main-fina-2-release. Test Finalize VINTF, Finalize SDK, and 2nd step/Finalize Android. Use local finalization to build and copy presubmits.
- 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.
Dry run:
Full cleanup. Remove all local changes and switch each project into head-less state. Also removes "DryRun" branches. SDK. Perform SDK finalization and upload the CLs to Gerrit. SDK and REL. Perform SDK finalization, plus all necessary changes to switch configuration to REL, and upload the CLs to Gerrit.