You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
At the moment, when an automated bamboo branch is added, it is named after the git branch. For example:
feature/XX-1234
becomes:
feature-XX-1234
Is there away to change the automated naming convention? In my particular case I would like the branches to include the original creators name:
{branchName}-{user.name}
example:
feature-XX-1234-john.doe
This would help developers in our team be able to identify which branches are theirs. We all so send broken builds to a slack channel for back merging and need to alert the correct developer, doing this off the last person to commit is not always accurate here.
Unsure of how to achieve this? Happy to install any plugins
Would it be possible to add the the name of the creator as a suffix to the git branch when created? Then it will propagate to Bamboo.
Otherwise you will have to create the branch manually in Bamboo and then choose the display name.
Regards
Lasse Langhorn
Would it be possible to add the the name of the creator as a suffix to the git branch when created? Then it will propagate to Bamboo.
We thought of this, it would make our branch naming far too messy.
Otherwise you will have to create the branch manually in Bamboo and then choose the display name.
This is kind of what we are doing, once they get automatically created we change the branch display name to include the devs name. Anything that requires manually work however is a pain. It would be optimal if we could automate this. If it is not possible are there any future plans to implement this feature?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.