You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello, my bamboo-home directory is quite big (almost 15 Gb) so I'd like to know if there is a way to "clean-up" some logs or any other "non so useful" files.
Fyi on my plans I only keep the last 2 build logs, not more.
Thank you in advance
Jerome
Hi Jerome,
You can configure Global Expiry (see https://confluence.atlassian.com/bamboo/configuring-global-expiry-289277253.html), which gives you the option of cleaning up unused artifacts.
Cheers,
Christian
Premier Support Engineer
Atlassian
Hi Christian, thanks for your answer. Here is the setting I get.
Maybe this mean that I cannot really purge more information? (fyi the size actually reached more than 20 Gb now)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jerome,
We have seen cases where Global Expiry tries to clean up artifacts but then fails due to some underlying error. I wonder if that is the situation here - try triggering global expiry using the "Run now" button and then take a look at the atlassian-bamboo.log in <BambooHome>/logs to see if you can spot any errors.
Cheers,
Christian
Premier Support Engineer
Atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, the result is "The expiry affected 19 builds and no deployments" and I did not see any easy-to-see error in the log. I guess this means that ther is no other reason to reduce the size which is probably normal. I'll investigate with my team, thanks for your time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome!
One thing that I just wanted to point out - based on the screenshot above you're excluding builds from expiry if they have one of the "sprint" labels. It could be that the builds contributing to the storage consumption have one of those labels and are therefore not expired.
Cheers,
Christian
Premier Support Engineer
Atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.