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
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
I am trying to restrict the ability of developers to build the master branch, they need to be able to build, compile and test their branch(es) but not build against master database
Hello @Dave Grandon
You can work externally on Bamboo to restrict the merger of changes to the master/main branch by implementing a Pull Request and approval mechanism. That way your developers will be able to push their changes to their own branches and only merge to master when a Pull request is approved and merged.
Another strategy you can adopt is to modify Bamboo in a way that the repository attached to a Plan does not have "master/main" as the default Branch. For that, you need to modify the repository settings and declare another branch as the default.
You can then modify the Plan permissions to allow developers to only run builds and not edit the Plan.
If you want to have full control over the changes to the Plan structure, you can consider migrating the plan to Bamboo Specs (configuration as code).
Atlassian Support APAC
--please don't forget to Accept the answer if the reply is helpful--