This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

What is an agent?

An agent is a service that runs Bamboo builds. There are two types of agents:

(Note: Local agents run in the 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.)

What is a capability?

A capability is a feature of an agent. A capability can be a:

  • builder (e.g. Maven)
  • JDK
  • custom capability (a key-value property which defines a particular characteristic of an agent, e.g. 'operating.system=WindowsXP' or 'fast.builds=true')
  • Perforce (location of the P4 client application, if Perforce is being used as the source repository)

機能は、エージェント固有として定義することも、すべてのローカル エージェントまたはすべてのリモート エージェント間で共有することもできます。エージェント固有の機能の値は、同じ名前の共有機能 (存在する場合) の値をオーバーライドします。


See Configuring Capabilities.

How are capabilities used?

A requirement is an agent capability required by a build plan.

Together, capabilities and requirements control which agents can execute builds for particular plans. Each plan can only be built by agents whose capabilities meet the plan's requirements.

Matching can be specified as either a regular expression or an exact match. See Specifying a Plan's Capability Requirements.

How are builds distributed to agents?

An agent will consume a single plan at a time and block until that build is complete. If you'd like to build multiple plans concurrently on the Bamboo server then simply setup multiple local agents. If the agents are remote, then you'll need to install that number of agent instances on the machine. Separate installations are required because each remote agent will need its own home and log directories.

Error rendering macro 'gliffy'

java.lang.IllegalArgumentException: Content must not be null

How do capabilities affect the distribution of builds to agents?

Error rendering macro 'gliffy'

java.lang.IllegalArgumentException: Content must not be null