Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to reduce bamboo-home size?

jgauthier March 21, 2018

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

1 answer

0 votes
Christian Glockner
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2018

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

jgauthier March 21, 2018

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)

bamboo expiry.png

Christian Glockner
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2018

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

jgauthier March 21, 2018

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.

Christian Glockner
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2018

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events