Do not cancel builds on same branch if another workflow is triggered

[jimmydieng_tophat]

I agree! Having Rolling Builds turned on breaks this feature https://blog.bitrise.io/start-multiple-builds-with-the-same-trigger

If I spawn multiple builds (different workflows) with the same branch and have Rolling Builds enabled, then a only the last build will be running.

EDIT: Guess there is an issue reported for what I just described too.

'Bitrise Build Start' step aborts current workflow if Rolling Builds is set to cancel running builds

We want to start using parallel builds as described on https://blog.bitrise.io/start-multiple-builds-with-the-same-trigger to save a lot of build time. We have Rolling Builds enabled, and set it to auto-cancel running builds. Now, as soon as the main workflow starts a second workflow with the ‘Bitrise Build Start’ step, the main workflow gets aborted with reason “Automatically aborted via Rolling Builds.”. The obvious workaround is to disable the “Running builds” option in the Rolling Builds …