-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
Currently, there's a mechanism for disabling a particular branch plan, but there's no way to disable the main plan to give preference to a branch; in the case of a hotfix, where code may be pushed into both development and a hotfix branch contemporaneously, being able to disable the develop branch to give precedence to the hotfix branch would make a significant difference in the time to test-completion if there's contention for agents.
The only way it seems this is possible now is to wait for the develop lines to kick off and then manually stop them, which is less than ideal.
[BAM-12833] Provide mechanism to disable main plan but allow branches to run
John Knight
added a comment - Exactly what I was looking for!
Thanks Piotr! Hm... So maybe you're after a different features, like for example
(I don't see you to be a watcher of those issues, so I reckon you might be unaware of them - and they seem to be relevant to your use case IMO)
John Knight
added a comment - Technically, in this case, this is exactly what we did. The issue was filed for two reasons: 1) in a rapid set of iterations around a hotfix, we may have code being committed to both the hotfix branch and development simultaneously, but need the hotfix to take priority – with an unlimited number of agents, this would be moot, but unfortunately we're not atlassian 
in this case, manually firing the hotfix branch across dozens of plans eliminates the benefit of having everything in a CI server to begin with.
2) It just struck me as strange and something I'd never thought of before.
John Knight
added a comment - Technically, in this case, this is exactly what we did. The issue was filed for two reasons: 1) in a rapid set of iterations around a hotfix, we may have code being committed to both the hotfix branch and development simultaneously, but need the hotfix to take priority – with an unlimited number of agents, this would be moot, but unfortunately we're not atlassian in this case, manually firing the hotfix branch across dozens of plans eliminates the benefit of having everything in a CI server to begin with.
2) It just struck me as strange and something I'd never thought of before. Hi John,
Looking at your description I'm wondering why you can't use following workaround:
1) disable main plan (via plan configuration -> actions -> disable plan)
2) enable (or leave enabled) the hotfix branch (via plan configuration -> hotfix branch -> actions -> enable branch)
3) whenever a new code is pushed into development and hotfix just start a manual build of 'hotfix' branch
I understand that there is some bigger problem, and my suggestion is not enough. May I ask what is missing? Do you need the 'hotfix' branch to be auto-triggered, without the need of manual prod? Or is it something different?
regards,
Piotr Stefaniak
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Bamboo Team