it's highly ironic that the bamboo remote agents lack this very very very very (repeat 100 times) basic feature while Bamboo licensing strategy is based on how many remote agents you have...

Any plans around that?

Ran into this issue with automatic branch management branches leaving working directories on the agents. Are there any updates on this issue? Thank you

I found that Bill Neff's script has a couple important bugs in it, related to the regexes and wild cards.  It will delete lots of directories that it doesn't mean to.

Here's a fixed version:

ls $BAMBOO_AGENT_HOME/xml-data/build-dir/ | perl -ne 'print if s/^([A-Z]+-[A-Z]+\d+)-.*$/$1/' | sort | uniq | perl -nle '$status = system(qw(curl --fail -I -s), "$ENV{BAMBOO_URL}/rest/api/latest/result/$_", qw(-o /dev/null)) >> 8; if ($status == 22) {print "$_ is expired.  Delete."} elsif ($status == 0) {print "$_ is still active"} else {print "Unknown status for $_"}'

I didn't include actually deleting the items - left as an exercise.

Thank you very much for your interest and support for this improvement request. With great pleasure I'd like to announce that we've decided to qualify this issue onto our short term roadmap.
Please watch this issue for future updates.

Krystian Brazulewicz
Atlassian Bamboo Development Team

Just chiming in, we're starting to ramp up our remote agents and licences (and of course, paying the associated cost for them now) and this is becoming absolutely critical for us.  We've got scripts and hacks all over the place to keep 10 odd remote agents in check which is becoming harder to manage and account for.

@bneff that script is a huge step for us in the right direction, thank you.  It's a bit unreliable though as we're not really checking if the fail is project not found in bamboo, or if the fail was API issue/network/auth/something.  But we'll look to continue with that line of thinking though. So thank you again

Cassius, so, we do essentially the same, except that we just delete everything older than "7 days", or to bring the disk down to 70% full, which hits first instead of deleting only the expired/deleted plans.

We then have a plan with enough jobs that theoretically every agent, if they were doing nothing, could run them in parallel, and that every agent is needed. In practice, of course, some will be doing something, but that's fine. This then checks the directory, and does the deletion. This is then run every hour. Sometimes agents are missed, but in general, every agent is hit every day, and in this way you can use Bamboo to clean itself up. Which is really something that we want Atlassian to implement!  Especially since this solution only probabilistically cleans every agent, instead of guaranteeing that every agent is hit x times per day.

Thanks Bill.

This actually sounds like it would be a reasonable way to go about it.  Unfortunately our agents are containerized and doing cron jobs in containers is a no-no   Perhaps we can run cron jobs on the agent/container hosts that simply instantiate new containers that attach to the build-dir persistent volumes and run your script and exit.  Then we may be cooking.

We run that script on every remote bamboo agent.