✈️ How to level up your releases with Runway — Webinar, Feb 8th at 1pm ET — Register
✈️ How to level up your releases with Runway — Webinar, Feb 8th at 1pm ET — Register

Auto-generated tester notes, directory sync, automatic triggers for build buckets, expanded rollout metrics, and more

Release management

Keep users and roles from your directory provider synced to Runway – and even all the way to App Store Connect and Play Console

If your company is on the larger side, chances are you’re managing your organization’s teams, users and their permissions from a centralized directory like Okta, Microsoft Active Directory or similar. But up until now, for user and team management within Runway, admins have had to do things manually. Now, with directory sync support, Runway integrates with your company’s directory provider to take care of everything automatically for you: from assigning new users the correct roles and app membership, to updating users who change teams along the way, to deactivating users who leave your org.

Plus, you might remember that Runway also supports automatically syncing users and roles to App Store Connect and Play Console — so, combined with this new directory sync functionality, you can now automate user management all the way from your org’s centralized directory to the stores (something not available out-of-the-box from Apple or Google).

Get an even more complete and customizable picture of release health, with multi-integration support and new metric types

For many teams, getting a complete picture of release health means pulling from multiple different data sources, especially when it comes to things like performance monitoring and product analytics. To allow for this, you can now simultaneously connect as many of these kinds of observability and analytics tools as needed (Amplitude plus Datadog, say). Runway will pull signals from all of these sources into your Rollouts view and you’ll be able to configure health metrics attached to each and every one.

Additionally, we’ve added support for a number of new metric types: average, median, and 90th/95th/99th percentiles of property values are all now supported for most of our Observability & Analytics integrations, with even more metric types coming soon.  

Safeguard health and give your team peace of mind after-hours, with customizable blackout days and times for phased rollouts

Depending when you first kick off a phased rollout, it could be that a big step-change in user adoption will happen on a day – or at a time – when your team might not be quite as ready to quickly address any issues that arise. Now, you can avoid this by configuring blackout days and times during which Runway will temporarily pause your rollouts. For example, you can prevent rollouts incrementing over the weekend, or outside of normal business hours.

Highlighted quality of life improvements

  • Mark releases as “Skipped” in Runway, so you can easily advance past abandoned cycles while still retaining their history and position in your release timeline.
  • In addition to options to automatically apply a set of default ‘What’s new’ release notes or use your latest beta testing notes as release notes, you can now also carry over release notes from your previous completed release.
  • Quickly pull up the status of any release with our newly simplified release status Slack action: just type <code>/runway status [ios/android] [live/next/upcoming]<code> to get a snapshot of where things stand for any release.

Build Distro

Automatically group personal or team-specific builds, with user filters on build buckets 

One of the big goals with Build Distro is to make it dead easy to distribute and organize all the different build flavors your team cares about. Now, there’s an even more seamless way to handle personal and team-specific feature builds, with user filters on build buckets that automatically direct these sorts of early dev builds to the right place.

How it works is quite simple. If you’ve set up your bucket with a PR rule, only builds generated from PRs that were authored by the specified users will be pulled into the bucket. If you’ve set up your bucket with a branch rule (not pictured), only builds generated from commits that were authored by the specified users will be pulled into the bucket. Specify single users to create personalized buckets for WIP dev builds, or groups of users to create dedicated build buckets for different feature teams across your org.

Make it easier to generate any flavor of build hands-free, with customizable build triggers per bucket

Typically, teams are stuck between a rock and a hard place when it comes to getting the variety of build types they care about distributed: either trigger each different flavor manually all the time, or else set up and maintain a delicate web of conditional triggers in CI. With the addition of automatic workflow triggers on Build Distro buckets, you now get hands-free distribution for every different build flavor, with all the correct configurations taken care of for you out-of-the-box.

For example, consider a build bucket one of your feature teams has set up. It might have a PR rule configured that grabs builds associated with PRs against your main branch, authored by members of that team. Now, if you flip on the bucket’s build trigger automation, Runway will automatically generate new builds for that team whenever their members open or push to PRs against main (and then route those builds to the right place as usual).

Easily give testers full context with tester notes automatically generated from each build’s diff

Letting your testers know what’s new in a given build is a distribution best practice, but it’s also a tedious, manual step that quickly becomes error-prone and a drain on the team. Now, Runway can automatically generate and populate tester notes for you, based on the diff since the previous build of the same flavor. In addition to listing commit info, diff items link out to associated PRs and project management tickets, so your team gets the complete picture and things are easy to digest for technical and non-technical teammates alike.