I just realized that Rolling Builds settings don’t currently work, or at least do not bring the optimal/expected effect when we want to trigger more than one build (via Bitrise Start Build) for a given PR/push/tag (via trigger map).
Let’s say that when you push something to the PR
pr_to_develop kicks in and enqueues two builds -
ios_tests (Bitrise Start Build). When we make another push to that PR and
ios_tests builds are still in progress - they won’t get canceled, cause currently Rolling Builds knows only about
pr_to_develop and can cancel that at most (unlikely cause it’s pretty brief). Instead, new builds will be enqueued. Sth like that happens:
I have seen a ton of discussions/feature requests where people ask to develop a one-to-many (trigger to workflows) feature for trigger map, and as far as I see - we’re not getting into that direction. In such a situation it would be nice to at least improve that behavior.
When triggering multiple builds via Bitrise Start Build and Rolling Builds setting is enabled.