Build matching

Wherever Runway surfaces build information in the platform and in notifications, we try to show both CI build info and app store build info for full context. We also use the relationship between CI builds and store builds to power certain automations. For example, Runway’s automation to tag each release traces from the store build that was released to the CI build that generated it, and uses the commit info on the CI build to know exactly which commit should be tagged.

Because there’s no actual link between CI builds and store builds, Runway needs to perform matching between builds. There are a number of factors used for this matching, each of which is given different priority. These include:

• Build numbers (identical or overlapping, e.g. CI build #123 and store build #12345)

• CI artifacts (if you have enabled artifact handling by Runway, we are able to access store build info on CI artifacts)

• Relative timing (CI build start/stop times versus store build upload timestamp)

• CI build status

Certain factors guarantee 100% match success, such as identical or overlapping build numbers, but if your team doesn’t adhere to such conventions, Runway can still match builds successfully in most cases.

If your team runs many overlapping RCs or release builds and higher priority matching factors aren’t available, Runway can occasionally mismatch builds. This can cause confusion, so we recommend adjusting your build numbering and/or enabling build artifact handling in Runway if possible. Otherwise, you can contact us to have build matching disabled via a backend configuration.