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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Disable planbranch cleanup in database for specific branches


As I've learned so far (Planbranch cleanup option in database), the planbranch setting "Clean up plan branch automatically" is stored in the Bamboo database in the table BUILD_DEFINITION (column: XML_DEFINITION_DATA):


 With the column being an NTEXT column, it is kind of laborious, if the switch would have to be toggled, I would have to work with temporary tables, doing casting, etc.

Isn't there an easier way to disable the setting "Clean up plan branch automatically" (i.e. the XML_DEFINITION_DATA value) automatically for specific branch types (i.e. bugfix/)?

Both two expiry settings need to be taken into consideration:

  • cleanup due to git delete branch
  • cleanup due to branch inactivity

Is the only chance to look for bugfix/ branches in the tables and set disabled to true in the XML?


1 answer

1 accepted

0 votes
Answer accepted

Hello @HeWi,

Unfortunately, a programmatic way to enable/disable the branch cleanup is not available in Bamboo.

Please check the following feature request for more details. Make sure to follow and vote it so you'll get notified of any future implementations of it. You can even add your specific case as a comment; that will help the developers prioritise it and consider it as a candidate.


Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

Hello @Eduardo Alvarenga ,

that's what I did guess, but very interesting to see, that others have already thought about the same problem, thanks for the link to the feature request. Unfortunately I don't have much hope, only 7 Watchers, created in 2017 already, not many responses, but nonetheless I did add a comment.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events