Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

what takes precedence - build expiry or branch inactivity settings


  I have a question I hope I can get some help with.  We are using branch build labeling to keep released builds from being automatically deleted.  We are using the global expiry settings to not clean up an builds with 'release' or 'rc' labels on them.

However, branch plans that have the branch inactivity setting configured to delete a branch plan after 30 days of source inactivity seem to be over riding the global expiry setting of not removing builds labeled with release.

Over the holiday break we had a number of released branch plans deleted that includes builds that had the release label applied to the builds we deployed.  Soo... we lost of a large number of released builds in Bamboo due to this.

So the question is - can someone please help to clarify what takes precedence when it comes to branch build clean up - branch plan activity settings or global expiry labels?

Thanks in advance for any help with this.  


Oh and we are running Bamboo ver 5.9.3



1 answer

0 votes

First of all: build result expiry and deleting plan branches that are inactive are 2 very different things. In the first case you delete results in the second entire plan branches

When you delete a plan (or plan branch) result expiry is not checked: if you decide to delete entire plan, it means plan and all of its results.

I guess you could say that, in a way, branch inactivity has precedence over build expiry, but that's not precise description of things.

Note that you can prevent individual branches from being affected by branch automatic removal by setting an option on Branch Details tab.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

969 views 4 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you