We’re very excited to announce the launch of Build Distro, a better tool for mobile build distribution that makes it dead simple to get the right builds into the right teammates’ hands! 📲 🚀
Build Distro allows you to clearly define and group the different types of builds your team distributes — from one-offs and work-in-progress dev builds, to staging builds, to release candidates. You can avoid the usual jumbled pile of builds that folks have to carefully sift through, and give technical and non-technical team members alike an easier way to grab builds, with streamlined installation via QR or Slack link. With hassle-free distribution, your team can check out builds earlier and more often, improving collaboration and app quality.
Continue reading below for all the highlights, and check out the Build Distro docs to get started!
Build Distro introduces the idea of build buckets to allow you to clearly define and group different flavors of builds. Instead of having all distributed builds landing in that jumbled pile, you can now separate different kinds of builds using definitions based on branch, CI workflow, or some combination of both — or using more freeform, ad hoc buckets. Not only are build flavors logically separated into buckets, but you can set up targeted notifications and scope access per bucket to ensure the right people are aware of and able to seamlessly install new builds relevant to them.
With branch-based and ad hoc, personal build buckets, Runway makes it much easier to share work-in-progress builds. You can create dedicated buckets for test builds and nightlies on your main development branch or any feature branches, and everyone on your team can also have their own personal buckets to drop updates into as they work. Product managers, QA, designers, and other engineers and stakeholders can now easily grab any WIP builds, earlier and more often during the development cycle, helping your mobile org improve quality and shift left.
One of the worst failure modes around build distribution has to do with test or staging builds getting accidentally shipped to production. It may be rare, but when it happens, it can be devastating. Confusion around distributed build flavors is often to blame, and Runway’s build buckets remove this risk. Clearly delineate prod and pre-prod builds, and scope access accordingly.
Even once someone has tracked down a build they want to check out, actually getting it onto their device comes with its own hassles. Runway makes installation foolproof and seamless: with each build, you can install directly by scanning a QR code or sending yourself a link in Slack. Plus, alongside each build you can see full context on the build flavor and exactly what work it contains — no more guesswork, pinging build numbers back and forth and hoping you’re grabbing the right version of the app.
Getting up and running is simple: connect your existing CI and… that’s it. Once you’re connected, Runway will get you started with a few default shared buckets for development and RC builds, and anyone on your team can easily create scoped personal buckets. To define a new shared bucket, simply select a branch and a workflow (from among any defined in your CI, automatically pulled in by Runway) and builds will start populating the bucket with no further intervention.
Exactly how you leverage Build Distro is up to your team. You can spin up Build Distro by itself and use it as a standalone tool. Or, for a tightly integrated experience across the entire dev and release cycle, Build Distro plugs seamlessly into Runway’s end-to-end release management platform as a beta integration, allowing you to manage everything to do with pre-prod builds and testers alongside the rest of the release context.
With Build Distro, the Runway platform is unlocking yet another aspect of a more collaborative and streamlined mobile development experience for teams — not just for engineers, but for each and every role and stakeholder involved. We would love to hear your thoughts, and invite you to reach out for a personalized, guided tour!
And stay tuned for more: our roadmap includes Build Distro iterations that will tackle things like provisioning and signing, triggers and other bucket-level automations, and even more ways to create and share one-off dev builds.
Runway can now take over the upload step of your CI/CD pipeline, automatically grabbing artifacts from CI workflows and sending them to destinations you specify. Not only does this save you precious build minutes, but Runway’s automatic retries help eliminate flakiness and the need to babysit things.
Configuring uploads is easy and flexible: simply select which CI workflows to upload from, point Runway to any specific artifact files to upload (tokenized patterns accepted), and choose particular destinations to upload to. Runway will automatically perform the uploads on each workflow run, retrying failed uploads if needed and optionally notifying your team about the outcome of every upload.
For more details on getting started with the artifact upload automation, head to the Runway docs.
Producing installable builds for testing as part of your CI/CD workflow is the easy(ish) part. Actually getting those builds into your team’s hands, seamlessly and without confusion, can be challenging. Now, you can share foolproof installation links in just one click: right from the Artifacts module of each build in Runway, send a link to teammates in Slack that will allow them to easily install the build onto their own device without any hunting around or extra steps.
‍
Life isn’t always as simple as Android & iOS, or GitHub & Jira. We know that Runway teams are shipping their products across various different platforms, and using various different tools in the process. Continuing our mission to cater to every flavor of mobile (and mobile-adjacent) team, we recently added support for:
Since we started Runway, a lot of folks have come to us motivated to automate their entire release process and improve collaboration around mobile, but lacking an important prerequisite for getting fully integrated in Runway — namely, CI/CD.
Turns out that, despite the GUIs and workflow builders that are now the norm for cloud CI, and despite the awesomeness of fastlane, people still struggle to get an end-to-end pipeline stood up. It’s not their fault: even with the GUIs and workflow builders and fastlane, everyone still has to reinvent the wheel. You need to piece together the right steps, gather the right configs, store the right secrets, perhaps even write some Ruby and random YAML flavor-of-choice…
At Runway, we think mobile CI/CD should be the easy part — a true out-of-the-box unlock. That’s why we’re launching Quickstart CI/CD, a free tool for growing teams and indies that can autogenerate a complete build-and-deploy pipeline for Android or iOS in minutes.
Simply run the wizard and let Runway do the heavy lifting. There’s no lock-in to worry about, and you’ll be able to build on top of the pipeline as your needs grow. Under the hood, Runway is assembling all the necessary steps, configs, and secrets, then generating CI-native config files to merge straight into your repo or take with you wherever you like.
We're excited for everyone to try this out! Click here to get started.
We know that getting late-arriving fixes into a release post branch cut can be an annoying exercise. Depending how your team does things, you might be delicately cherry picking changes over onto the release branch, wasting time fix by fix, or else you’re relying on cumbersome backmerges post-release (and dealing with the all-too-common mess that arises when said backmerges are inevitably forgotten!).Â
Runway’s newest automation streamlines the process of getting fixes into a release by automatically cherry picking specific work that your team flags from the working branch into the appropriate release branch. Any PR that contains a designated, customizable pattern in its title is actively monitored by Runway — as soon as it’s merged into the working branch, Runway will cherry pick the relevant commits and open a PR against the specified release branch. If you also have the “merge Runway PRs” automation enabled, the fixes will be auto-merged once required checks pass — there’s nothing more your team needs to do.
Runway automates away lots of manual tasks throughout the release process, and in doing so, it produces many artifacts along the way. Think pull requests, commit messages, GitHub releases, etc. Runway auto-generates relevant messages and copy to go along with each of these, but teams have told us they want more control over this kind of metadata — to do things like add Conventional Commits prefixes or tailor release changelogs to their liking.
Now, you can customize the strings that appear in Runway-generated artifacts. Take Runway’s version bump automation, for example — the PR that Runway creates with the version bump commit can now be configured with:
To allow for dynamic, relevant text, these custom string definitions support a number of special tokens that can pass in info like the release version, release branch name, CI and store build numbers, release pilot info, and more.
Head to the “Custom strings” section on your app’s settings page to check out the full list of custom string options.
We’ve continued to build on Runway’s new feature flagging integration with the evergreen aim of making Runway the single source of truth for all of your tools, throughout the entire dev and release lifecycle. To pull in additional context teams have been asking for, clicking into a specific feature flag opens up a new detail drawer, surfacing properties like target delivery rules and audiences. From here, you can now also toggle the feature flag on and off to quickly update its status without leaving Runway.
And, we’re happy to announce that we now support LaunchDarkly as our newest feature flagging integration, with more providers coming down the pipeline.
We know folks are relying on Runway’s release pilot rotation to share release responsibilities across their team, so we’ve made it easier to manage exactly who’s on duty, and when. In addition to adding and removing team members from the list of pilot-eligible users, you can now order and reorder the list to configure the exact rotation you want to run.Â
Feature flagging is a powerful way to gate in-progress functionality, run experiments, and decouple product launches from binary updates — but wrangling feature flags can be tricky. It takes time and effort to make sense of all your flags, keeping tabs on what needs to be enabled for the first time, or deprecated, and when exactly. Release pilots, PMs, and others bounce between their team’s feature flagging platform and other tools to understand dependencies and stay on top of everything.
Now, Runway can help your team make sense of your feature flags. You’ll be able to see all feature flags that are relevant to a given release, including details like each flag’s status, rollout percentages, and specs for any associated variations, alongside the rest of the release and rollout context you’re used to in Runway. A special callout is applied to feature flags that are of particular interest in a given cycle — making it easier to see at-a-glance which flags might need extra attention during the course of the release’s rollout or beyond.
Optimizely is the very first feature flagging provider you can plug into Runway, and future integrations will include LaunchDarkly, Unleash, Firebase Remote Config, and even in-house solutions. You can help us prioritize – which tool does your team use for feature flagging?
The launch of Runway’s Rollouts feature, and with it our new Observability & Analytics integration point, has allowed teams to monitor release health more holistically. And now, you have even more options for where signals of health are pulled from. Does your team use Mixpanel or Datadog? Connect it in Runway, select key metrics that define “healthy” for your team, and automate alerting and rollouts based on thresholds you set.
