Configuring agents
A Bamboo agent is a service that can run job builds. There are the following types of Bamboo agents:
local agents run as part of the Bamboo server.
- remote agents run on computers, other than the Bamboo server, that run the remote agent tool.
- elastic agents run in the Amazon Elastic Compute Cloud (EC2).
Local agents run in the Bamboo server's process, i.e. in the same JVM as the server. Each remote agent runs in its own process, i.e. has its own JVM.
Each agent has a defined set of capabilities and can only run builds for jobs whose requirements match the agent's capabilities.
If you are looking for information on elastic agents, please refer to the documentation on Working with Elastic Bamboo.
On this page:
Creating a new agent
To create a new agent, see:
Configuring an agent's capabilities
To configure an existing agent's capabilities, see:
Disabling or deleting an agent
To disable or delete an agent, see Disabling or deleting an agent.
Notes
- A capability is a feature of an agent. A capability can be defined on an agent for:
- an executable (e.g. Maven)
- a JDK
- a Version Control System client application (e.g. Git)
- a custom capability. This is a key-value property which defines a particular characteristic of an agent (e.g. 'operating.system=WindowsXP' or 'fast.builds=true').
Capabilities typically define the path to an executable that has already been installed, and must be defined in Bamboo before Bamboo or its agents can make use of those.
Capabilities can be defined specifically for an agent, or they can be shared between either all local agents or all remote agents. Note that the value of an agent-specific capability overrides the value of a shared capability of the same name (if one exists).