How to configure Bamboo to automatically delete offline remote agents
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
By default, standard remote agents are not automatically deleted after they go offline. This may lead to a large list of offline remote agents to delete manually through the Bamboo web interface.
When an offline agent is deleted, its capabilities and assignments are also removed. This means that other agents may take over performing builds of the previously deleted agent.
Environment
Bamboo Data Center 9.6.3 and newer
Solution
To ensure that standard remote agents are deleted after they enter the "offline" state, set the bamboo.delete.remote.agents.on.going.offline system property to true and restart Bamboo.
For example:
-Dbamboo.delete.remote.agents.on.going.offline=trueTo learn how to set Java system properties and startup options for Bamboo, see Configuring your system properties.