Diagnosing and Resolving Disconnected Bamboo Build Agents
A diagnostic guide for resolving 'Disconnected' or 'Unavailable' Bamboo build agents, covering JVM heap issues, JRE mismatches, network timeouts, and disk exhaustion.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A diagnostic guide for resolving 'Disconnected' or 'Unavailable' Bamboo build agents, covering JVM heap issues, JRE mismatches, network timeouts, and disk exhaustion.
Artifact Retention and Disk Space Atlassian Bamboo uses a configurable artifact cleanup policy to manage disk space on remote agents, typically governed by the "Keep last N builds" setting. This mechanism is designed to prune expired artifacts from the agent's directory structure based on the build plan ID during the build lifecycle. There is uncertainty reg
Agent Configuration Synchronization Atlassian Bamboo agents utilize a local cache of build plans and configurations to optimize execution. This system relies on a heartbeat mechanism and versioning checks to ensure the agent remains synchronized with the server's current state. Cache Inconsistency Scenarios When a disconnect occurs between the agent and the