Release candidate
Last updated
Last updated
The Release candidate step communicates the status and history of builds from your Release candidate CI workflow, and provides controls to automatically or manually specify which builds are selected for subsequent steps in the release process.
Starting with the Release candidate step, Runway will assist you in keeping track of your desired Release Candidate (RC) through the build process, regression and beta testing, upload and selection and submission to the app stores for review, and ultimately releasing the app update to the store. By default, Runway assumes that the latest build from your CI provider is your target RC, but provides the option to manually select a different build if necessary.
Runway will automatically select your latest uploaded build in the app store if the Select the latest build automation is enabled.
The active build module will display workflow status and information about your active build. This will be the latest build that Runway has detected from your Release Candidate CI workflow, unless an earlier build has been manually selected (or ‘frozen’) as the active build for the remainder of the release process.
Information available here includes: Build status, CI build number, timestamp of latest workflow status, commit info (branch / commit / message), and artifact download links if present. If Runway was able to link the RC build to a matching upload in the app store, a corresponding app store build number will be shown as well.
Click the CI build number link to jump to your CI provider's workflow details view.
Runway isn’t always able to match a CI build to your selected build in the app store. This can occur if a build was manually uploaded to the app store, or if commit info is missing from your build in CI. Read more on build matching here.
At the bottom of the view, Runway shows a count and a list of all builds (including status and build information) detected from your RC workflow for this version.
Release pilots, or other team members with sufficient privileges, can click the Lock as active RC button to lock that build in as active for the remainder of the release process.
This will affect the target build that is the focus of Regression and Beta testing steps, as well as the build selected in the app stores in preparation for submission and release.
If you have the ‘Select the latest build’ automation enabled and you manually lock a particular RC build, Runway will suspend automatic selection of your latest uploaded build in the app store.
You can revert a manual selection by clicking the Resume auto-selecting latest build action above the history list.
You can add checklist items to this step by visiting the Checklist tab.
Checklist items cover any unique parts of your team's release process and live across all your releases. Steps with checklist items won't be marked as complete (green) in Runway until all checklist items have been completed (in addition to the normal criteria that would mark a step as completed).
