Disabling or deleting an agent
Configuring agents
このページの内容
関連コンテンツ
- Setting up plan build dependencies
- How to trigger a branch after successful build of another branch with a different name
- Triggering builds
- Bamboo repository polling trigger does not start the build immediately
- Repository triggers the build when changes are committed
- How do I work with Triggering builds
- Running a plan build manually
- How to start up Bamboo with build plans, deployment environments, branch detection and build status updates disabled
- Bamboo plans queued for extended duration when a single Linked Repository is used by multiple plans
- How to configure Bamboo plans to be triggered by specific repository directories
Bamboo allows you to disable or delete an agent, to prevent that agent from running any further builds.
- Disabling an agent lets you keep the agent in Bamboo, but stops it from running builds.
If you need to prevent Bamboo from building any plans at all (e.g. while you re-index Bamboo), you can disable all agents. By doing so, all builds will wait in the queue until you re-enable the agents.
Deleting an agent removes it from Bamboo altogether. If you need to use the agent again in future, you will need to recreate it (see Creating a local agent and Creating a remote agent for more information).
Note that you can also delete/disable individual plans and/or their jobs. This prevents the plans and/or their jobs from being submitted to the build queue. See Disabling or deleting a plan and Disabling or deleting a job.
To disable (or delete) an agent:
- Go to
> Build resources > Agents. A list all agents that currently exist in your Bamboo system will be displayed. The Status column indicates which agents are currently enabled or disabled. Scroll down if you require remote agents.
- Select the checkbox for the agent (or agents) you wish to disable or delete.
- Select the Disable (or Delete) button above the table.
Last modified on Mar 5, 2024
関連コンテンツ
- Setting up plan build dependencies
- How to trigger a branch after successful build of another branch with a different name
- Triggering builds
- Bamboo repository polling trigger does not start the build immediately
- Repository triggers the build when changes are committed
- How do I work with Triggering builds
- Running a plan build manually
- How to start up Bamboo with build plans, deployment environments, branch detection and build status updates disabled
- Bamboo plans queued for extended duration when a single Linked Repository is used by multiple plans
- How to configure Bamboo plans to be triggered by specific repository directories
Powered by Confluence and Scroll Viewport.