Kickoff
Last updated
Last updated
The Kickoff step serves as an overview for code and branch-related details, as well as pilot and planning information that may be helpful as your release process is getting started.
Modify basic parameters about your release here:
Release version (required) - Enter the planned version number of your next release. Runway will determine whether it's a major, minor, or point release based on semantic versioning rules.
Release pilot - Choose a specific team member to act as release pilot for this release. If no selection is made, Runway will automatically assign a release pilot from a rotation of team members who are eligible to be release pilots for this app.
Target kickoff date - Specify a target date for when you plan to kick off this release.
For release branch teams, Runway considers a release kicked off when a release branch is detected or created by Runway.
For static branch teams, Runway considers a release kicked off when code is detected past the last release tag, or when Runway promotes code from your development branch to your release branch.
Target submit date - Specify a target date for when you plan to submit this release to the app store for review.
Target release date - Specify a target date for when you plan to release this app update to end users.
This action will remove the record of this release from Runway's list of planned app versions.
Here, you'll see a list of labels / fix versions used in your project management tool that are associated with ticketed work for this particular release. Runway uses feature affiliations to track work items that are intended to go out with the release but might not be in the actual code yet (and, optionally, can add missing labels / fix versions to tickets that have associated code that is already part of the intended release).
You can set up or manage feature affiliations from the Integrations settings page.
Shows the status of the branch that your release will be built from.
Release branching teams - Runway checks for a matching release branch for this specific version.
If the release branch was created by Runway (via automation or using the Create branch button at the bottom of the Kickoff step), you'll see a link to the associated PR here.
If Runway's attempt to create the release branch was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.
Static branching teams - Runway monitors the branch you release from to detect new commits past your last release tag.
If code promotion was performed by Runway (via automation or using the Promote code button at the bottom of the Kickoff step), you'll see a link to the associated PR here.
If Runway's attempt to promote code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.
You can change the details of your branch setup from the Integrations settings page. Runway may not be able to accurately determine the status of your release if this information is incorrect.
Runway detects where your version may be determined in your code, and shows you the status of the associated code on your working branches as well as the branch you'll release from.
Runway can bump the version in code on your behalf by using the Bump version button at the bottom of the Kickoff step. Once the version bump is performed, you'll see a link to the associated PR here.
If Runway's attempt to bump your version in code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.
The name of the tag for the previous release and a link to the code diff in your version control system (e.g. GitHub).
The name of the associated pilot for this release. This can be changed by editing release settings.
You can enter notes here about anything your team needs to keep track of for this version release. These notes are internal to Runway and not visible to app store users. Markdown is accepted.
For example, you might call out in the release description that a major feature is being modified and needs extra attention from the team during the release process.
You can use the buttons at the bottom of the Kickoff step to perform key actions during your release kickoff.
Runway detects where the app version is referenced in your code and bumps it to match the version number of the current planned release.
Once the version bump is performed, you'll see a link to the associated PR shown along with version in code information on the Kickoff step.
If Runway's attempt to bump your version in code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.
(Release branch teams) Runway will create a release branch for this version.
Once the release branch is created, you'll see a link to the associated PR shown along with release branch information on the Kickoff step.
If Runway's attempt to create the release branch was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.
(Static branch teams) Runway will promote code from your working branch to your main branch.
Once code promotion has been performed, you'll see a link to the associated PR shown along with release branch information on the Kickoff step.
If Runway's attempt to promote code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.
You can configure the following Kickoff automations by visiting the Automations tab on this step:
Editing automation settings from an individual release will apply those changes to all of your upcoming releases for that app.
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).
