# Quickstart

## Get started in 5 easy steps

<figure><img src="/files/hx1Dnwx3Ac5btzEsB1r4" alt=""><figcaption></figcaption></figure>

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.

{% hint style="info" %}
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](/using-runway/build-distro/build-distro-buckets.md#default-buckets) section.
{% endhint %}

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

{% hint style="info" %}
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](#making-artifacts-from-your-ci-cd-workflow-available-for-download) section.
{% endhint %}

{% hint style="warning" %}
The following build system integrations are not supported with Build Distro:

* App Center Build
* TravisCI
  {% endhint %}

4. **\[iOS only]** Connect with App Store Connect to unlock additional build distribution features like [automatic device provisioning](/automations/types-of-automations.md#sync-provisioning-profile-devices). This step is optional.
5. 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.

<table><thead><tr><th width="194">Supported Provider</th><th width="265">Artifacts available by default?</th><th>Additional Info</th></tr></thead><tbody><tr><td>Bitrise</td><td>Yes</td><td><a href="https://devcenter.bitrise.io/en/builds/managing-build-files/build-artifacts-online.html">https://devcenter.bitrise.io/en/builds/managing-build-files/build-artifacts-online.html</a></td></tr><tr><td>GitHub Actions</td><td>No</td><td><p>Add an "upload artifact" step to your build job in your GitHub Actions <code>yml</code> file.</p><p><a href="https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts#uploading-build-and-test-artifacts">https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts#uploading-build-and-test-artifacts</a></p></td></tr><tr><td>GitLab CI</td><td>No</td><td><p>Use the <code>artifacts</code> keyword in your GitLab CI <code>yml</code> file.</p><p><a href="https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html">https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html</a></p></td></tr><tr><td>CircleCI</td><td>No</td><td><p>Add a <code>store_artifacts</code> step to your CircleCI job's <code>yml</code> file.</p><p><a href="https://circleci.com/docs/artifacts/#uploading-artifacts">https://circleci.com/docs/artifacts/#uploading-artifacts</a></p></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.runway.team/using-runway/build-distro/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.