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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,461,674
Community Members
 
Community Events
176
Community Groups

How to handle multiple repos with a single plan in bamboo?

Hi, I am dealing with many repositories where I want to create a single Bamboo plan. I could connect all the repositories and I want them to trigger build based on check-in into a specific repo. But bamboo server checks out all the repository when starting the build. Is it even possible in Bamboo?

1 answer

0 votes

Hi, can you please describe use case.

It's possible to use several repositories in Bamboo plan. It's possible to configure trigger to start build only when changes happened in some of plan repositories, not all of them. Does it answer your question?

Hi Alexey, Thanks for replying. I have configured more than 100 java repositories to my build plan.  But every time something changes in one of the repo it checks-out all the repositories. How do I configure that sort of trigger. Can you give me some pointers?

What kind of trigger do you need/use? There's Repository polling trigger which has checkbox for every repository you added to plan. You can uncheck some repositories if you don't want to run build on this repository change. At the same time Bamboo will checkout code from all repositories if you have checkout task for each of 100 repo.

What checkout tasks do you use?

Does your plan require source code from all 100 repositories?

It's really massive configuration, hope you use Bamboo Specs to manage it

Hi Alexey, That's where the problem I have. Even though I have repo polling trigger enabled but it checksout all the repos I have in checkout task. I don't want the server to be inflated with all the unnecessary repos even though I clean the directory after every build. But checking out more than hundred repos would be highly unacceptable.

Deleted user May 17, 2018

Checkout the 100 repos in separate plans (which trigger automatically on a new commit).

You can then still have your "parent" or "uber" plan which downloads artifacts from those other 100 repos/plans.

Hi, I am also using single BAmboo plan which has 10 repository and 10 branches. But i need to run each and every branch individually. But everytime only default repository getting build trigger. How to configure that what branch i am running that repository need to get executed.

How to configure such in bamboo.

Please let me know

Same issue here.

Our use case
We're having hundreds of different npm packages, each in separate repositories. We're publishing them into our own private npm registry. We want a package/repository to be published automatically on post-commit to master.

The best would be if I would be able to attach a Bamboo plan to a Stash project, so the plan would run for all contained repositories.

Hi Vincze,

 

Thanks for responding could you please share me some sample plan configuration for the same. It will be helpful to verify and proceed further.

 

Waiting for your kind response.

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events