Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

how to modify soucecode checkout repo in multiple deployments?

Hi Team,


I have some 400 deployment projects available, i would like to change the old linked repository to new repository.


Is there any API or any step is bamboo can help me to do this?




1 answer

0 votes

Just to state/clarify the obvious, the main purpose of using Bamboo's linked repositories rather than configuring one per plan/project is to separate repository changes from plans/projects that are consuming them:

Linked repositories are available globally to all plans and jobs configured on the Bamboo server. Doing this can save you from having to reconfigure the source repositories in multiple places if these ever change - any changes to a linked repository are applied to every plan or job that uses that repository. 

Can you please clarify whether you actually need to change which linked repository is consumed rather than changing which repository the linked repository itself references (of course, you might e.g. want to change the repository only for a subset of consumers, but not others)?

Other than that, I'm not aware of a resp. REST API, unfortunately Bamboo does not expose its features via REST in a consistent way - speaking of which, there is also no REST API for linked repository configuration itself, please watch and vote for for the following improvement to increase Atlassian's priority to close this gap:

That being said, you might be able to achieve this via the Java API by means of the excellent ScriptRunner for Bamboo (BETA), which allows you to automate Bamboo via Groovy. You need to figure out the required code yourself though , i.e. I haven't yet tried to adjust the repository configuration via that route.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events