How do people retain bamboo builds which have gone into production, without them being caught up in the bamboo retention policy to make effective use of disk capacity on the bamboo server?

[Bedelia Wolverton-Kettrick]

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?

Many Thanks

[Alexey Chystoprudov]

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.

https://confluence.atlassian.com/bamboo/deployment-projects-338363438.html

[Bedelia Wolverton-Kettrick]

We do use deployment projects, but I'm unsure how you can configure the expiry to skip such builds without using labels, can you elaborate please Alexey?

[Alexey Chystoprudov]

Use global expiry - https://confluence.atlassian.com/display/BAMBOO/Configuring+global+expiry

[Bedelia Wolverton-Kettrick]

Thanks Alexey,

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?