Quickstart
Last updated
Last updated
Follow these steps to get started with Build Distro by Runway.
Navigate to the build distribution page in your Runway app.
Click Get Started. Note that only admin users in your org can opt your app into Build Distro.
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 Default Buckets section.
[Recommended] Connect a supported CI/CD integration and configure your workflow settings. This step is optional – you can always manually upload builds to buckets.
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 Making artifacts from your CI/CD workflow available for download section.
The following build system integrations are not supported with Build Distro:
App Center Build
TravisCI
[iOS only] Connect with App Store Connect to unlock additional build distribution features like automatic device provisioning. This step is optional.
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.
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.
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.
