Comment on page
Azure Repos
- 1.Select an app in the top left corner from the Switcher
- 2.Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar
- 3.Click on Integrations in the sidebar
- 1.Find the Azure Repos integration module under the Version control section
- 2.Click the Connect button – you’ll be taken through a standard Azure DevOps App OAuth flow
- 3.Azure Repos will redirect you back to Runway
- 4.Select an Azure Repos project and repo to associate with your app in Runway
- Runway uses this to read tags from Azure Repos and delineate your releases, and also to generate tags when auto-tagging releases upon completion
- Pattern accepts the string
{version}as a stand-in for the release version, e.g.v{version}
Runway expects version strings that adhere to Semantic Versioning principles — formatted as
x.y.z (representing major.minor.patch).- For GitFlow or similar, pattern accepts the string
{version}as a stand-in for the release version, e.g.release-ios-{version}- You can assign different patterns to different types of releases using the Release type dropdown
- Omit pattern for trunk-based, e.g.
main- Be sure to select all types in the Release type dropdown
- Working branch: your main working branch, e.g.
development - Staging branch: if you create your Release Candidate builds from some branch other than your release branch, set that here
- Deploy branch: if you create your final builds from some branch other than your release branch, set that here
Last modified 6mo ago