Automatic build expiry configuration

Norbert

Hi

I'm using the build expiry feature from Bamboo
so far so good, but is there a better way to select which builds should be deleted?

I have some "release" builds triggered from Jira, but as far as I understand there is no way to automaticly label it, or except this builds from the cleanup builds task.

Is there some way to "protect" this build, except giving them a label add this label to the exception list.

Adam Myatt2

Labelling seems to be the only mechanism to prevent builds from getting removed by the Buold Expiry Mechanism. If the global expiry doesn't work for all your Plans you can certainly override it at a Plan level to tweak to be Plan-specific. There's a Bamboo Task plugin that allows you to automatically tag a Plan, but that probably doesn't help you as you want to auto tag builds if they are triggered from Jira.

Seems like this could be a feature request to Atlassian at jira.atlassian.com where you would want to suggest that Build Expiry can work with variables and/or labels. When a Bamboo plan is triggered by Jira the plan results have an Overwritten Variables section" that sets variables such as jira.projectKey, jira.baseUrl, etc. It would be cool to be able to say if these variables exist then do not expire.

OR a plugin to auto-tag a build result with a label that is set to not expire if those Jira variables are set.