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 settings, but this causes a lot of unnecessary builds for us.
Sorry for the delayed answer!
The Tooling Team has a ticket for this, but itās not solved yet.
For now, you canāt use the āBuild Startā step with the Rolling Build option if the āCancel Running Buildsā option is set.
Thanks for the update! Is there any timeline for a fix? We currently have two tasks which both take 10-15 minutes, which canāt run in parallel because of this issue as itās something thatās running on pull request not using āCancel running buildsā can cause a lot of running builds, so we donāt want to use that at the moment.
Sorry for the delay and for keeping you waiting! Unfortunately, we canāt really provide an ETA, there is a ton our Tooling Teamās plate sadly but rest assured they are working on resolving this as we speak!
Thanks for your patience and understanding in the while, we will definitely get back to you once we have an update!
Sorry about the delay! Some urgent changes came up and unfortunately so our Tooling team couldnāt prioritize this task due to them, but they are working on resolving this and will notify this thread once they are done.
In the while, feel free to contact us on our on-site chat about these problems to see if thereās something else we could recommend!
Thanks for the update @bitce! We ended having to remove the āBuild Build Startā workflows, and putting everything into a single workflow. Itās a lot slower now as things arenāt parallel, but at least builds get auto cancelled on new commits.
Was there a technical reason why Bitrise couldnāt allow multiple workflows to be triggered from the same trigger? (or multiple duplicate trigger conditions that start different workflows)
Sorry to bother again, but is there any update? Weāre now at 45 minutes build times - thereās at least two things running for 10-15 minutes each that could be parallelised, but weāre blocked by this issue.
This is different to the feature request as an existing feature thatās supposed to parallelise steps is not working with rolling builds enabled.
This is wasting a lot of time for us as we have to spend a lot of time waiting for CI to finish and is causing a huge amount of frustration.
@marianeum This is so frustrating! The only work around I can think of is put parallel workflows into separate apps. And use different triggers on them.
@bitce This is getting a little bit ridiculous. It shouldnāt be that hard to fix right? Since all the parallel builds have the same build number, the newer ones could JUST cancel the builds with the same trigger that also have a smaller build number. Whatās so hard about that?
Weāve just rolled out this feature, from now on only builds triggered on the same workflow gets aborted when a new build is started. Thanks for reporting the issue and let me know if you have any questions!
as itās something thatās running on pull request not using āCancel running buildsā can cause a lot of running builds, so we donāt want to use that at the moment.