I have Bamboo configured to run builds every time new commits are detected in one of a few different repositories. For reasons that aren't very relevant for this question, we only want to run builds on the tip of master, so one of the first things we do is ensure our checkout point matches origin/master. If we have multiple people pushing code around the same time, we sometimes have builds that fail due to the checkout point not being origin/master. Currently these builds are being flagged as failures as they do not contain useful build artifacts, but they also don't typically contain any issues that need resolving as a new build will be triggered immediately after this one completes.
Is there a way to have a build register an error instead of a pass/fail so we can better identify when we have a real issue we need to deal with?
Benajmin, does it mean that it is not possible to build your project/run tests from any revision but tip of the master? Removing this restriction seems like a way to fix the problem of your false failures.
Answering your question Bamboo has only 2 states for finished build: SUCCESS or FAILURE. We're not planning on adding any other states.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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