When using the global expiry policy in bamboo to make effective use of storage capacity on the bamboo server. We would use labels to indicate a build to be preserved. We have a concern that the labels however could be deleted without our prior knowledge, leading to a build which is in production being expired and removed.
Has anyone found a way to restrict deletion of labels once applied to perhaps a group of administrators to mitigate the risk of build being expired incorrectly due to deleted labels?
One of the approach to track build results used for release is Deployments feature. User links build result to named release and configure expiry to skip such builds. If you don't use Deployments feature you can use this approach instead of labels.
My concern is that the label could potentially at a later date be deleted accidentally or maliciously.
Then when the expiry policy executes it's rules the build will be expired as it no longer has the label.
Has anyone found a way to mitigate this risk?
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
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