Probably not, though this depends on your retention needs for the build and deployment artifacts etc. - please see section /xml-data/builds/ within Bamboo server home directory (also applies to Bamboo agent home directory) for details:
This is known as the Build Directory. This is where Bamboo stores build results (note that they will be deleted as described in Configuring global expiry). Its contents can be backed up as per Exporting data for backup.
Contains the build results for all the builds belonging to the JOB_KEY plan. Each build result is an individual XML file. Do not edit these files or the corresponding information in the database may become corrupt.
Contains the logs for each build belonging to the JOB_KEY plan.
As hinted upon in the first paragraph, rather than manually cleaning up those build directories, the recommended way to deal with old files is Configuring global expiry according to your business needs:
Global expiry allows you to manage the timing for when build and deployment artifacts should be deleted from your Bamboo system.
You may want to consider doing this for the following reasons:
- Build and deployment artifacts can be large, and so consume storage on your system. Your system may run out of disk space if artifacts no longer in active use are retained indefinitely.
- Large numbers of builds and deployments clutter the Bamboo user interface, and may reduce performance, making it slower to work with Bamboo.
See this Atlassian blog post for a discussion of using build expiry and labels.
Thanks Steffen, sometimes when I run my plan it fails right away showing it could not clean up xml-data>build-dir>jobname>lib
So I log in to server and clean up the lib folder in that folder and rerun the script. It works after the clean up. We also clone plans to create new ones. Is it better to create new plan rather than cloning?
Thanks again for the info.
Cloning plans is completely fine, and so is manually cleaning up (part of) the build folder in exceptional circumstances like you are doing there for 'lib', insofar most of the files are temporary build results anyway - I just wanted to make sure you are aware that the main build artifacts and logs are also stored there and could be accidentally deleted in principle, hence the recommendation to resort to the built-in automatic expiry mechanism by default.
@Jayasree Tadanki - I highly recommend to ask a separate question for each separate topic: This provides the best chance for a qualified answer, because everyone monitors the title and tags of new (!) questions to check whether one has the specific know how to provide a valuable answer (in other words, comments to 'old' questions like this one are rarely noticed by anyone but the few initial thread participants).
For the same reason, please also 'accept' my answer as solution via the checkmark on the left side so that it doesn't show up as unanswered anymore, thereby keeping others and myself focused on and motivated to assist with new questions :)
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs