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
  • Get started in 5 easy steps
  • Making artifacts from your CI/CD workflow available for download

Was this helpful?

  1. Using Runway
  2. Build Distro

Quickstart

PreviousBuild DistroNextUploading builds for distribution

Last updated 6 months ago

Was this helpful?

Get started in 5 easy steps

Follow these steps to get started with Build Distro by Runway.

  1. Navigate to the build distribution page in your Runway app.

  2. Click Get Started. Note that only admin users in your org can opt your app into Build Distro.

  1. [Recommended] Connect a supported CI/CD integration and configure your workflow settings. This step is optional – you can always manually upload builds to buckets.

The following build system integrations are not supported with Build Distro:

  • App Center Build

  • TravisCI

  1. That’s it! If you've connected and configured a CI/CD integration, builds will start to populate in your respective buckets, and you can start installing by clicking “Install” on any installable build on a bucket.

Making artifacts from your CI/CD workflow available for download

Runway's Build Distro can help your team get build distribution set up in just a few steps as long as your team is already generating binary artifacts from your CI/CD workflow and making them available for download. For some CI/CD integration providers, making build artifacts available for download is the default behavior, so nothing needs to be done in order to get Build Distro set up in Runway. For other providers, you may have to add an export step to your CI/CD workflow to make build artifacts available for download by Runway. See the table below for more details on how to make build artifacts available to be pulled into Runway Build Distro for your provider.

Supported Provider
Artifacts available by default?
Additional Info

Bitrise

Yes

GitHub Actions

No

Add an "upload artifact" step to your build job in your GitHub Actions yml file.

GitLab CI

No

Use the artifacts keyword in your GitLab CI yml file.

CircleCI

No

Add a store_artifacts step to your CircleCI job's yml file.

Runway will automatically generate some default buckets for your app to get you started. To learn more about the buckets that are created by default, go to the section.

Your CI/CD workflows must be configured to output installable artifacts in order to work correctly with Build Distro in Runway. To learn more about how to configure your CI/CD workflows to output binary artifacts, see the section.

[iOS only] Connect with App Store Connect to unlock additional build distribution features like . This step is optional.

🎛️
Making artifacts from your CI/CD workflow available for download
https://devcenter.bitrise.io/en/builds/managing-build-files/build-artifacts-online.html
https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts#uploading-build-and-test-artifacts
https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html
https://circleci.com/docs/artifacts/#uploading-artifacts
automatic device provisioning
Default Buckets