Hi,

With the release of Bamboo 5.9 we have improved the way branches are cleaned up. You will now have more options to get your branches automatically cleaned up when the branch is removed from the repository.

I'd like to thank everyone for their patience, we really appreciate the trust that you are putting in us.

Sten Pittet
Bamboo Product Manager

Is this the same request as this one https://jira.atlassian.com/browse/BAM-13129? Why Atlassian development teams did not run into this problem? Are they not using Bamboo or not doing Agile (Gitflow workflow) themselves?

To clarify my comment,

I was suggesting two distinct delete alternatives. The user would be able to choose one.

Alternative A - delete the branch when Stash deletes the branch.
Alternative B - delete the branch after X days of inactivity (this exists today)

With possibly an enhancement to alternative A. Where -

Alternative A++ - delete the branch after X days of Stash branch deletion.
0 days means delete immediately when Stash deletes the branch.

Main trouble is - if you want to delete branch after X days of deletion in Stash/git you need to remember in Bamboo when it was deleted and periodically search for Bamboo branches eligible to delete - as there will be no more events about it.
Not a big deal but a little more complicated than just deleting branch.

Configurability for Bamboo branch deletion would seem appropriate here.

• delete branch synchronized with Stash branch deletion
• delete branch after X days of inactivity

There is a new plug-in Plan Branch Terminator for Stash fom Mibex Software GmbH which addresses this

It seems the only way to have old feature branches automatically removed is to set an expiry, correct? Unfortunately this then runs into BAM-12161, where a branch which doesn't receive commits for awhile not only has its plan deleted, it will NEVER run again.

I agree with Pawel that the plan branch shouldn't immediately be deleted, but should instead be cleaned up after some time has passed.

Immediately deleting plan branch with all results when it's deleted in repository is questionable.
It may be ok for ones but to soon for the others. I would do it after N days - configurable on plan level.

Still looking for some forward momentum (or a glimmer of hope) on this cleanup feature request. We are in "maintenance Hades" as it stands.

This is struggeling us too.
We use the git flow and delete branches after merging via Stash pull requests.
We have about 10 branches per day.

The minimum functionality for us would be:

• No error generated in Bamboo (or configurable), this is not an error scenario but daily valid business
• Bulk action: "delete branches" with some AND-ed selection criteria (deleted in stash, older than x days, unused for x days, disabled, manually created, matching regexp, notmatching/matching a label) etc.)