Bamboo uses a ton of disk space, with no easy way to keep it to a managable level. The logs for running it are constantly inflating with output of checking the repositories for updates. Fortunately it seems to limit the filesize to 20MB, and keeps only 5 levels of history for a total of 80MB of logs. That's an upfront cost that should never change. It would be nice if these logs grew at a slower pace (or if there was an option to reduce the amount of logged info.)

Build output can grow beyond reason, though. It's often useful to have a continuous build that has logging turned on, so you can see what's going wrong when something goes wrong, but each build can then balloon in size. We're at a point where Bamboo writes ~1GB per day. We've temporarily set the builds to expire every 2 weeks, but that isn't an ideal situation – we really want to keep them around forever (or close to forever).

Some suggestions for managing ballooning disk space:

• Archive builds older than X days, unarchived upon request (spidering disabled, etc..).
• Store build output in zipped format, unzipped upon request.
• Enable finer-grained expiry controls pt 1. (Per project, plan, on-demand build, etc..)
• Enable finer-grained expiry controls pt 2. (Options to expire only: selected artifacts, log output, test results, etc...)

I'm sure there's a ton of other things that can be done too.

Thanks!