Build Distro Buckets

Buckets are groups of builds that can be automatically shared with a group of bucket members that you define. Buckets are a great way to group together the same kinds of builds (think release candidate builds, development/alpha builds, or even feature team builds) so there’s no ambiguity about the kinds of builds that are available for testing in a given bucket.

All apps will come with default buckets: the Release Candidate bucket, and the Development bucket. Certain users will also have Personal buckets created by default.

In addition to the default buckets, custom buckets can also be created. Try creating a bucket for your WIP feature or for your team.

Bucket settings

Buckets have properties that can be configured to refine the kinds of builds that are available in a bucket and who has access to them. The following properties can be configured on any build bucket:

• Name: the display name of the bucket.

• CI/CD workflow: the workflow that Runway should look for when pulling build artifacts to populate the bucket.

• CI/CD workflow branch: the associated branch that the specified CI/CD workflow is run on. Required if a CI/CD workflow is defined. Runway will pull build artifacts from any workflow run that matches your specified workflow + branch pair.

• File names: the file names or file name patterns of the binary build artifacts that should be pulled into the bucket. If no file names are specified, all .ipa artifacts will be pulled into the bucket for iOS platforms, and all .apk artifacts for Android platforms

• Org-wide access setting: enable org-wide access to make your bucket available to all users in your Runway org. Anyone in your Runway org with access to the bucket link can view and install builds from the bucket. If this setting is disabled, only bucket members can view and install builds from the bucket.

Note that only bucket admins can update a bucket’s settings

Uploading builds to buckets

There are currently two ways to upload builds to a bucket:

• Configure a CI/CD workflow + branch pair on the bucket and Runway will automatically pull build artifacts from matching workflow runs into the bucket. Note that your CI/CD workflow must be set up to make the required build artifacts (the `.ipa` or `.apk` files) available in order to use this option

• Upload builds manually to the bucket using the build upload flow on the bucket details page. You can upload .ipa files to buckets on apps of iOS platforms, and .apk files to buckets on apps of Android platforms

Other ways to upload builds to Runway build distribution buckets are coming soon.

Default buckets

Runway will by default start off with three distinct buckets: Release Candidates, Development, and a personal bucket.

Release Candidates bucket

The Release Candidates bucket can be used to group together release candidate builds – by default, it’s configured with your app’s Release Candidate CI/CD workflow and release branch, as defined during the setup flow of your CI/CD integration.

Release Candidate buckets will by default include all org admins as well as any app users with at least one role as bucket members. Org admins will be included as bucket admins. Other roles will be included as bucket testers.

Release Candidate buckets will start out with Org-wide access enabled. You can disable this setting from the bucket's settings.

Development bucket

The Development bucket can be used to group together development or alpha builds – by default, it’s configured with an association to your app’s Development CI/CD workflow and working branch, as defined during the set up flow of your CI/CD integration.

Development buckets will by default include all org admins as well as any app users with at least one role as bucket members. Org admins will be included as bucket admins. Other roles will be included as bucket testers.

Development buckets will start out with Org-wide access enabled. You can disable this setting from the bucket's settings.

Personal bucket

By default, any user with an admin role in the org, or any user in the app with a PM, EM, or Engineer role will get a personal bucket. These buckets are designed as freeform workspaces – a bucket where you can upload any kind of build to share with whomever you like.

Personal buckets aren’t associated with CI/CD workflow by default, and don’t include any members besides the owner of the personal bucket.

Notifications

The notifications tab in the bucket details shows a list of available notifications for the given bucket. Notifications can be toggled on and off at the individual bucket level, and customized so that notifications for a given bucket can be sent to different channels of your choosing.

Bucket notifications are enabled by default on the Release Candidate and Development default buckets.