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 Crashlytics
      • 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

Was this helpful?

  1. Quickstart CI/CD

Quickstart CI/CD overview

Quickstart CI/CD is a standalone tool that helps teams easily spin up a build-and-deploy CI/CD pipeline using fastlane and GitHub Actions. It works by scanning your repo for the necessary configuration details to set up your workflow, and automatically generating the necessary files to get a build-and-deploy GitHub Actions workflow up and running.

Support for additional CI/CD providers is coming soon!

By the end of the Quickstart CI/CD wizard flow, you'll have a GitHub Actions workflow ready to go that does the following:

iOS

  1. Checks out your repository and installs Ruby dependencies using bundler

  2. Installs CocoaPods, Carthage, or NPM dependencies based on your configuration

  3. Fetches the latest version and build number from TestFlight and increments the build number by one

  4. Loads your signing certificates into the keychain, fetches and installs provisioning profiles from App Store Connect

  5. Builds and signs your app with your specified configuration

  6. Uploads the generated .ipa to App Store Connect

  7. Uploads the generated binary to the GitHub workflow's artifacts

Android

  1. Checks out your repository and installs Ruby dependencies using bundler

  2. Installs NPM dependencies if needed

  3. Fetches the version codes from the Play Console and increments the version code by one

  4. Builds and signs your Android app with your specified configuration

  5. Uploads the generated .apk or .aab binaries to the Play Console

  6. Uploads the generated files to the GitHub workflow's artifacts

The generated workflow is a great starting point for getting your team set up with CI/CD for mobile apps of both platforms. From here, there are lots of ways you can extend your new workflow to suit your team's needs.

The Quickstart CI/CD wizard will take your project's scanned values (along with any specific configurations you've defined in the Confirm and complete your build’s configuration step), and input the relevant fields in the resulting yml and fastlane files.

Any fields that were left unspecified during the Quickstart flow will need to be manually updated in the resulting files. Templated fields are specified with curly brackets like so:

{ FIELD_NAME } , for example: { RUBY_VERSION }.

Cross-platform React Native teams

If your team is shipping a cross-platform React Native app, you can still use Quickstart CI/CD to generate a functioning GitHub Actions Workflow for each platform, but there are a couple of things to keep in mind:

  • You must run through the Quickstart CI/CD wizard once for each platform. You can connect the same repository to both runs of the wizard.

  • Each run will output a separate GitHub Actions Workflow file that will build and deploy your app for the specified platform.

  • The Quickstart CI/CD wizards assumes your repository doesn't already have an Appfile and Fastfile and creates new instances of these files. The second run of the wizard will as a result attempt to overwrite the output of the first run – we recommend manually merging the two outputs by choosing the Download files option at the end of the process.

If you choose to open a pull request for the second run of the wizard, we highly recommend closely examining the resulting pull request to ensure that any previously added functionality in your repository's Appfile and Fastfile is not unintentionally removed.

PreviousApp configuration filesNextGetting started

Last updated 1 year ago

Was this helpful?

🛠️