Hi @exuper okouya,
if I understand you correctly, you're using build plans to actually perform deployments. I'd recommend separating builds (with tests) and deployments - by introducing the Bamboo Deployments feature: https://confluence.atlassian.com/display/BAMBOO/Deployment+projects. If I recall correctly, it's available since Bamboo 5.
With actual deployment projects, you have to define releases (aka deployment versions) based on build plans. When creating a release, you have to explicitly select a build number - and this would mean that the person to create a release would have to choose a red build intentionally to perform the scenario you described.
Also, deployments can be configured to be launched automatically after a successful build.
For more information regarding deployments feature in Bamboo you can look for "related pages" under the above link.
The case is this:
for every project APIs, web app, etc... we have two sets of plans:
recently we eccountered a problem that is someone in the organisation launched a deploy job on a master branch with a build status failed.
After a postmorterm we have decided to search and implement a solution to make sure deploy plans are blocked when the correponding continuous integration plan indicate a build status failed.
Hopefully my explanations are clear.
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