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?
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?
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.
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.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events