The commit isolation functionality in Bamboo is really useful for highlighting which check in has caused a break.
One problem we've found is that upon re-enabling a disabled plan, the runs continue for all checkouts that occurred whilst the plan was disabled. Is there a way to prevent this and to tell it to only start running for each commit since a certain revision?
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot