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 was reading the Atlassian post here:
It says that per-plan repository configurations are being deprecated and that one should use linked repositories instead. I don't understand how this is going to work. We have several hundred developers who may want to create their own plans and we are planning to move away from using mono repositories. This implies we may have to create several hundred linked repositories. Since creating a linked repository requires "create repository global permission", we will either end up with a lot of people with that (potentially dangerous) permission or my DevOps team will become the bottleneck for developers to create their own plans.
Maybe I'm not thinking about this correctly. Can someone explain?
Hello @Andy Barclay welcome to the community! :)
Yes, as of Bamboo 7.0.3, creating plan-level repositories is not the advised way of creating repositories.
At the same time, we are aware that the workload for admins in Bamboo is considerably increased with the deprecation of the same plan-level repositories and we still didn't move forward with the decision. I am very interested in knowing your use-case and understanding better how we can improve your situation, would you mind sharing more details? My email is email@example.com :)
I am one of 3 global administrators for bamboo and we have 700 developers. A large number of them are using bamboo and we are moving away from a mono repo. Without plan-based repos, any time a development team creates a new repo, they must reach out to one of the three of us to create the global repo. Ideally, there would be project-based repositories. That way, the admins for the project could create repos accessible to the whole project (I would say normally, projects are team-based, so it make sense for a repo to be available to a whole team).