This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

A Bamboo agent is a service that provides capabilities to run Job builds. There are two types of Bamboo agents:

(info) 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.)

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 for more information.

On this page:

How Do Capabilities Work With Requirements?

A requirement is specified in a Job and defines the capabilities which are required by an agent to build that Job.

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

See Configuring a Job's Requirements for more information.

How Are Builds Distributed to Agents?

An agent will consume a single Job at a time and block any other Bamboo Jobs from being processed until that Job build is complete. If you would like to build multiple Jobs simultaneously on the Bamboo server, then simply set up multiple local agents. If the agents are remote, then you will 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.

How do Capabilities Affect the Distribution of Builds to Agents?*

関連トピック

For more information on configuring agents and capabilities, see the following topics:

  • ラベルなし