I've been dealing with this issue in BAM-13094.
Having thought about it a bit more, I think the UI and functionality for the "Branch Updater" is not sufficient. It's a good idea (automatically update from master) but it seems the implementation in lacking (in this issue and BAM-13094, it's not actually updating from master ... frequently enough).
Bamboo should implement (I feel) not "Branch Update from xxx" (intuitively, one would think xxx would be master) but "Branch Update from Parent". So, if we're using the terminology from Gitflow, an example would be:
- Branches from master (Develop branches) would being updated when there is a change in master
- Branches from Develop branches (Feature branches) would be updated when there is a change in its parent Develop branch
- If a change occurred in master it would cascade out to the feature branches (by first being merged into their parent Develop branches)
- If a change was limited to a Develop branch, then Bamboo would update only the Feature branches
Assuming Bamboo did update branches frequently enough from master, without the above you still run the risk of your feature branches drifting away from its parent Develop branch.
Hi everyone,
Thanks for your interest in this issue.
This request is considered a potential addition to our longer-term roadmap.
We'll typically review this request in about 6 months time, at which point we’ll consider whether we need to alter its status.
For the nearest future we've decided to prioritise other areas of the Bamboo roadmap, including:
You can learn more about our approach to highly voted server suggestions here.
To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Bamboo Team