we updated bamboo from 5.10.1 to 6.1.1. Now we miss a feature.
In Version 5.10.1 was it possible to disable a job for a branch. Now we can not disable a job for a branch, only for all branches.
We need this feature. Is there an other way to disable a job for a branch?
I'm afraid this has been a deliberate change based on Atlassian's observation that the behavior you've been relying on was considered a usability flaw, as further detailed in Disabling a job from the plan branch results does not disable the job for the main plan (BAM-18365):
Disabling a job from the plan branch results does not disable the job for the main plan. When you go to view the main plan and its job, the job shows as enabled.
The job will be disabled for that branch only. Because there's no way to tell if a job is disabled for only a branch in the UI, it appears from a user standpoint that the branch is missing the job entirely when the branch plan is run.
Ultimately this decision is for Atlassian to reason about of course, but given all other branch specific configuration is explicated on the dedicated branch configuration screen, I can understand that implicitly only affecting the branch you are on when disabling/enabling a job is a fairly subtle detail that's easy to trip over accidentally.
Of course, I can see how the former behavior might be helpful to structure your build - can you describe your particular use case, maybe there's another way to achieve the desired outcome?
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs