We have a question.
How is bamboo agent selected? What is the algorithm behind this.
Asking cause we ran into some issues that several agents were selected on the same host, this cause a lot of resource congestion.
Is there a way to make agent selection smarter? e.g. Select the agent with less io/cpu/memory usage.
Each agent has a defined set of capabilites and can only run builds for jobs whose requirements match the agent's capabilities. Together, capabilities and requirements control which agents can execute builds for particular jobs. If there is a match agent can execute the job, if not then job will not be executed since no agent will be available to cover that.
I know the 'capabilites' but what I am asking is 'capacity'
Does bamboo consider agent's capacity? as I mentioned above, we are use remote agent, there could be multiple remote agents located on one remote host. If a lot of remote agents which from same hosts were selected, then the JOB could be running really long.
Is there a smart way to assign agent based on host resource?
Yeah, but maybe if you add custom capability, as a simple key <-> value for the hardware defining high/medium/low performance servers you can maybe not dynamically, but execute more demanding jobs on better/faster machines, so that it would not be busy for other stuff.
G’day Bamboo customers, Bamboo DC 8.1 is now available with it the following features and programs: SAML 2.0, OpenID Connect, and Crowd SSO In order to help admins with a simplified user manage...
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