We're in a situation where we have hundreds (600+) of maven projects that we maintain. Will bamboo handle this huge amount of plans Or will things get out of hand? These projects all have common dependencies so some VCS changes will trigger a LOT of downstream jobs. Is there a recommended maximum or can anyone verify that they've successfully tried this?
This is no problem in principle, though the minimum CPU and memory requirements depend on the size and complexity of your plans, see Bamboo Best Practice - System Requirements for some Hardware considerations:
- Will your builds have functional tests as part of the plans?
- Are your plans executed simultaneously? If so, how many plans will be running at any given time?
- What are the requirements for your running builds, for example do they need large amounts of memory/disk/swap space?
- How many users will be using Bamboo at any given time? Like any web application, the system resource needed is proportional to the load experienced by the server.
- How many local agents do you plan on running?
According to the provided table, your requirements would probably ask for the outlined 16 core, 8 GB RAM, all remote agents setup, which can accommodate:
- 1000s of plans
- Frequent plan branches
- High concurrency
- High server use
According with the documentation you need a good configuration to do that.
Have a look in here
Incident response is a team sport, and customer support is an integral part of any team. While Ops is working hard to solve the problem at hand, support is on the front lines communicating with custo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs