We have a plan setup to do CI - it monitors the master branch of a Git repository with branch merging enabled, using the gatekeeper strategy and we have multiple agents enabled so we can build multiple plans. This works fine when different plans are building, but bamboo will build multiple branches of a plan and invariably, one of them will not push to the remote because it is behind the tip due to the other. Bamboo should not build multiple branches that have push enabled.
Just wondering if anyone figured this scenario out? We hit it today and are wondering how to resolve this. Right now we allocated the entire plan to only use a single remote agent to force serialization, but that is sub-optimal in scenarios where the agent is offline, etc.
We just aren't doing this anymore, especially since we're using pull requests in Stash with the auto-merge from release branches down to newer versions. We do still let Bamboo build other branches, and we require that they have 1+ successful build before we allow the merge.
Atlassian University Live webinars provide you and your teams with the chance to strengthen your Atlassian product skills, and learn directly from Atlassian experts. Learn how to earn our newest A...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events