By default, the CloudBees Build Acceleration installer configures a fixed number of agents. You can take it a step further by configuring the agent service to automatically start the number of agents according to the number of CPUs on the host.
A main benefit of this functionality is that this facilitates using a single image (such as an Amazon AMI, Azure image , or GCP image ) that you use for cloud bursting as a template across many different instance types, regardless of the CPU count on each type, to get the ideal number of agents.
|Enabling this feature requires manual modification of agent configuration settings as described below.|
Set the values of
Restart the agent service by entering:
sudo /etc/init.d/ecagent restart
Open Registry Editor.
In the following registry path:
set the value of the
agentCountregistry key to
Open the Services control panel, right-click the CloudBees Build Acceleration Agent service, and choose Restart.
On Windows platforms, you cannot start more agents automatically than were set during installation. If you plan to use