From Viktor Benei [bitrise staff] on 2016/01/14 14:09:23 +0000 There might be a case when you don’t want to allow multiple (usually deploy) builds to run concurrently. Even if we have more than 1 concurrency we might want to require one or more branch to only run one build at a time - for example w…

Makes sense, thanks for the details @neobeppe ! :slight_smile:

I would also love this feature! But instead of branches, would be awesome if we can limit concurrency for specific apps or workflows. In my case, we currently have two type of workflow: automated test workflow (which triggers on every new commits), and build workflow (which gets triggered daily, or…

[image] dvdchr-tvlk: I would also love this feature! But instead of branches, would be awesome if we can limit concurrency for specific apps or workflows. Specific apps: definitely, that should be covered with something like branch: "*" to match all branches. Workflows: good point, we’ll thi…

[image] viktorbenei: Workflows: good point, we’ll think about that, but right now I’m not sure if I have a use case for that (if we’d have branch based filters). Do you have a use case you could share? In our use case, we have a Bitrise workflow that gets triggered when someone pushes on our …

Definitely makes sense @dvdchr-tvlk , thank you for the use case & detailed infos! :slight_smile:

I have a user case for this also. For deployment of mobile apps. Deployment workflows can often involve incrementing build version numbers. I don’t want two deployment workflows running on concurrent jobs as they will both attempt to increment the version number and push back to github. This wil…

Description of the feature request Currently we have a plan for 3 simultaneous builds under 1 organisation. Is there a way to limit 1 build for project so that 1 project has only one simulationus build. We need this case as some projects would ask for 3 builds when they are triggered from 3 differen…

Hi @DeveloperExozet , Thank you for the feature request! I’m merging this thread to an already existing (and planned) one, which is about the same feature: [image] Limit concurrency on specified (deploy) branches, or on project/app level (only allow X concurrency for app Y) Website …

Hey there, sorry for the bump. I have a scenario in which one workflow (primary) starts a number of concurrent workflows at some point (through the Bitrise Start Build step). If I have 3 concurrencies available, if 3 primary workflows are executed, there will be a deadlock situation: the concurren…

Limit concurrency on specified (deploy) branches, or on project/app level (only allow X concurrency for app Y)

Feature Requests Website

viktorbenei October 25, 2017, 9:42am 16

Makes sense @DanielCreagh and it’s definitely planned, but we don’t have an ETA yet.

Assign concurrencies by platform

Topic		Replies	Views
Serialized workflow instances Builds	2	1226	August 23, 2017
Assign concurrencies by platform Question & Answer	3	1136	September 19, 2019
Is it possible to limit builds for project Builds	0	1435	June 18, 2018
Disable parallel app builds Builds	3	2020	June 6, 2017
Launch multiple machines and see the results on github PRs Question & Answer flutter	1	786	March 10, 2021

Limit concurrency on specified (deploy) branches, or on project/app level (only allow X concurrency for app Y)

Related topics