Let's say I have plans A and B, and B uses a shared artifact from A. One day I discover a fatal flaw in the software from plan A, but this is a new bug and I don't yet have a test for it. So I know that historically, the last 3 builds of A were affected by this critical bug, and I don't want any new builds of B to use the shared artifacts from those builds of A.
My problem is that I can't find a way to mark them as failed so that the shared artifacts will come from earlier versions. I anticipate this will occur many more times in the future as we discover new bugs that are not covered in the test results that currently mark a build as pass/fail.
Ideally, I'd be able to go click an X somewhere to mark those builds of A as "broken", and then the shared artifact would automatically come from the earlier valid pass. Any idea how to do this?
Yes, although I thought it may lead to confusion due to the fact that this "successful" build has been deployed to another server already. Deleting the build in bamboo seems like it would remove some of the history if someone wanted to investigate that build.
If that's the accepted way to deal with the situation, I'll run with it, but I wanted to make sure I wasn't missing something obvious that didn't involve removing history / logs out of bamboo.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello Community! My name is Claire Maynard, and I’m a Product Marketing Manager on the Bitbucket team. I’m interested in hearing what advice or tips you have for new users getting started on ...
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