Selecting a release candidate
In the release candidate stage you can specify a release branch, and select a Workflow that can generate an .ipa
or an .xcarchive
file for iOS apps, or an .aab
file for Android apps.
-
For iOS apps, the Xcode Archive & Export for iOS Step to generate the
.ipa
or.xcarchive
file. -
For Android apps, the Android Build Step to generate the
.aab
file. -
Deploy to Bitrise.io - Apps, Logs, Artifacts Step to deploy artifacts. It must be of version 2.2.3 or higher.
Once you select a branch and a Workflow, you can lock in the active build of that Workflow that will be used as the release candidate. By default, this is the latest build but you can lock in a different build instead.
Env Vars from Release Management
Release Management passes over certain Environment Variables to your builds at the Release candidate stage and later at the Release stage: Table 4, “Environment Variables passed to the builds from Release Management”.
To select a release candidate:
-
Open your release.
-
Select Release candidate on the left navigation bar.
-
Under the Configuration section, click the button.
This will open up the Configure release candidate dialog.
-
Select a Release branch and a Workflow using their respective dropdown menus.
-
Click Active build section.
. You will see the successful builds of the selected Workflow in the -
If you don't want to use the latest build as your release candidate, select a build from the Available builds list and toggle its switch in the Lock as RC column.
If you don't lock in a build, the latest build will be used as the release candidate.
When you have selected a release candidate, you can proceed to:
-
The TestFlight upload stage for iOS apps.
-
The Google Play upload stage for Android apps.