It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Disk space required by Bamboo keeps growing -> any way to manage this?

We found recently that our Bamboo installation was reaching the limits of it's disk space.

I have build expiry running nightly (keep builds for 1 week, minimum of 6), and this seems to clear up a few GB when run, but however this extra space disappeared very quickly after a few builds had been run. In practice, build expiry was running nightly, and any space that had been recovered was lost again by the morning.

On further investigation I found that the D: bamboo-home xml-data build-dir directory was massive (~20GB) and it wasn't being reduced when build expiry ran. I copied this directory elsewhere, and confirmed that Bamboo was functioning correctly without it, and am planning on deleting these files.

Is it safe for me to be deleting the D: bamboo-home xml-data build-dir directory?

Is there some in-built job in Bamboo that can manage the size of this? Some cleanup tool?

1 answer

1 accepted

Can you navigate to the miscellaneous tab of your job configurations and check the option Clean working directory after each build. This will clear the local copy of the repository available at<tt>D:\bamboo-home\xml-data\build-dir</tt> before each build. Please note that this may increase the time taken to run a build but will save space

How can this be set by default for all new job configurations, preserving build artifacts?

I am also looking for this. Is there a way to set as default?

Same for me, is there a way to set this as default or have it set in Bulk edit rather than going thru 300 different build jobs?

Is it save to manually delete the .svn / .git directories within build-dir\... ?

If you clean the working directory after the build, you lose any ability to properly troubleshoot a failed build. There must be a better solution than this, such as build history retention, artefact retention, configurable per plan/job

Additionally, the above suggestion does not get rid of old build logs or archived artifacts... which ins some cases are the real cause of disk space issues.

you lose any ability to properly troubleshoot a failed build

Agreed.  Is there not an open feature request already to resolve this?  If not I'll file a support ticket. 

It should be as simple as removing working directories older than N days, or keeping the last N working directories for a given plan.

See feature request BAM-13589 and vote for it

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Unable to add or edit Bitbucket Cloud repository in Bamboo

On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...

1,089 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you