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.
We're misusing branches to freeze quarterly versions. So every few months's we're duplicating the master branch.
Now our master gets build using a Bamboo Build Plan, and I've created the branch for our first frozen version and changed the branch of the repository - works fine.
Question is, on what the repository triggers react now?
Even if I do "Change trigger", I'm not able to set branches?
Hi Benjamin,
Thank you for reaching out to the Atlassian Community!
By default, the repository triggers will still respond to changes in any branch. In most cases, change detection will be run across all branches, and if the branch exists in Bamboo, a build will be triggered on that branch.
If you are using a Bitbucket Server repository, the Bitbucket Server Repository trigger will send a notification to Bamboo with the branch where the change occurred.
If you are on your frozen version branch, and select "Change trigger", the trigger the branch will use can be different from the main build plan. You won't need to choose a branch, because that should be found by Bamboo when the change notification is received.
I hope this helps. Please let me know if you have any questions.
Thanks,
Elias | Bamboo Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.