Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Navigate to the Integration settings view
  • Release tag pattern
  • Release branch patterns
  • Additional branches
  • Staging branch
  • Deploy branch
  • Feature affiliations

Was this helpful?

  1. Using Runway
  2. App settings

Integrations settings

PreviousRelease pilot rotationNextProfiles and devices

Last updated 6 months ago

Was this helpful?

Use the Integrations settings page to connect Runway to third-party tools that your team already uses as a part of your release workflow.

Navigate to the Integration settings view

  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

We recommend connecting your key integrations as a first step before filling in additional settings for your app.

Release tag pattern

Runway uses this to read tags from your provider and delineate your releases, and also to generate tags when auto-tagging releases upon completion.

The Pattern field accepts the string {version} as a stand-in for the release version, e.g. v{version}.Read more about .

Runway expects version strings that adhere to principles — formatted as x.y.z (representing major.minor.patch).

Do you tag all of your builds? That's great — you can keep doing that, but Runway will also need a unique, final tag to mark each release.

Release branch patterns

This is where you'll specify the naming convention for release branches. Runway can detect branches that are created with this pattern, or will use this pattern when performing automations to create branches.

You can assign different patterns to different types of releases using the Release type dropdown.

Are you a trunk-based team that doesn't use release branches? Omit the tokenized pattern, e.g. main

Be sure to select all types in the Release type dropdown.

Additional branches

Specify here other branches that are an essential part of your release workflow.

Working branch

Your main development working branch, e.g. development.

Staging branch

Set this if you create Release Candidate builds from a branch other than your release branch.

Deploy branch

Set this if you create your final, production builds from a branch other than your release branch.

Set this only if your deploy branch is different from your release branch.

Feature affiliations

Set up the fields (such as labels or fix versions) that will be used to categorize items for a given release in your project management tool.

  • Integration name - Choose the name of the associated tool

  • Affiliation type - Label, Fix version, etc (options will vary depending on the selected integration)

  • Affiliation pattern - Use a tokenized string here to associate tickets with a specific version, e.g. release-{version}

For such as GitFlow or similar, Release branch pattern accepts the string {version} as a stand-in for the release version, e.g. release-ios-{version}

Read more about .

Learn more about .

Read more about .

🎛️
version control
allowed tokenized patterns for tags here
Semantic Versioning
branching strategies
allowed tokenized patterns for branch names here
builds and branches in Runway
allowed tokenized patterns for feature affiliations here