Bamboo Artifact Cleanup Policy and Agent Disk Reclamation

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 regarding the synchronization of disk space reclamation when artifacts are removed through different triggers. Specifically, the behavior differs when the automated cleanup task executes versus when a user manually deletes artifacts via the Bamboo UI.

Given the risk of disk saturation on build agents, it is necessary to understand the timing of these operations. Does the server immediately signal the agent to purge files upon a UI-driven deletion, or is the agent's disk space only reclaimed during the next scheduled cleanup task or build execution?