-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
2
-
In BAM-18351, a flag to toggle branch cleanup for a particular branch was suggested as a new /plan/.../branch endpoint. This would allow admins to programmatically toggle the cleanup status of plan branches. However, it would also be beneficial to be able to fine-tune the plan branch deletion policy at creation time rather than have to go back after creation and push an API call.
In our use case, we have procedures that roll through a set of repositories and generate release branches. This works well; however, because we cannot fine-tune branch expiration based on a regular expression, we need to go into each of n release branches and manually uncheck the cleanup checkbox. We not only have to do this for releases but for certain long-running (but potentially idle) branches, which should remain in place until merged.
The ideal UI change would would allow for a regular expression to control expiration. The current UI looks like:
- Delete plan branch
After branch was deleted from repository
- # days
- After branch inactivity in repository
- # days
A more granular solution would look more like:
- Delete plan branch
- Only delete plan branches matching the expression:
- (regex box)
- After branch was deleted from repository
- # days
- After branch inactivity in repository
- # days
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-18532] Allow regular expression control of plan branch deletion.
This is still needed as of Bamboo 6.7.2. Reminder, with GitFlow, we have 100s of feature branches that need deleted. But we need to keep release branches for traceability and auditing purposes.
Please provide some insight into whether this can be exposed to the REST API (and Bamboo Specs) so that we can have more control over this.
Agreed. This feature is needed in order to use Gitflow with Bamboo. Currently there is no way to distinguish a feature branch plan from a release branch plan. Using Gitflow you delete your feature and release branches after you're done with them. But in Bamboo, we want to keep our release branch plans. So your current options in Bamboo are keep all branch plans (bad, tons of feature plans), delete all plans (bad, lose traceability), or manually manage the plan branches somehow (bad).
I totally agree, that this requirement is much needed. And as mentioned already, the manual work to be done is not acceptable. If implemented, the new feature should be available as a global admin option that is applied to each newly created plan branch. This will allow to create release planbranches having the checkbox "Clean up plan branch automatically" disabled automatically, beforehand, if the regex expression defined in the admin area matches. Just think about dependencies to other build plans- if the appropriate release branch (having the same name) does not exist anymore, the default planbranch artifact (from master planbranch) will get downloaded, and it is not possible to recreate the same release again.