> On Dec 27, 2018, at 10:31 AM, Joan Touzet <woh...@apache.org> wrote:
>
> Hi there,
> ----- Original Message -----
>> From: "Chris Lambertus" <c...@apache.org>
>
>> As a rule of thumb, we’d like to see
>> projects retain no more than 1 week or 7 builds worth of historical
>> data at the absolute maximum.
>
>> 54 GB ./CouchDB
>
> Our config is:
>
> Discard old items: checked
> Days to keep old items: 7 (for a long while now)
> Max # of old items to keep: 7 (newly changed - was blank)
>
> Can you let us know if this helps?
CouchDB has 300+ builds from July taking up 100-150MB each. I’m not sure why
these wouldn’t have been removed by the ‘days to keep old items’ parameter, so
we’ll need to look into that on the infra side as well. If the addition of the
‘max # of old items’ parameter doesn’t purge them after the next build, we can
remove them manually. If infra does have to go and do some manual pruning,
these are the types of things we’ll be looking for and removing.
Just looking at the build history in the Jenkins UI for the CouchDB ‘master’
branch, it’s clear that the ‘days to keep old items’ setting doesn’t seem to be
working at all, since you have saved builds back to November. Something else
we’ll need to look into. I doubt you were even aware of the July artifacts (I’m
not sure how you’d be able to see those.)
> I'm willing to look at more aggressive changes to reduce space,
> but would like to have a better understanding of how that space
> is being used. At a start it looks like we could try adding a
> deleteDir() command to our post { failure { ... } } block
> (declarative pipeline.)
>
> I'm off until Jan 6 on a desperately-needed vacation, so I can't
> really dig in until then.
Enjoy! Thanks for following up.
>
> -Joan
-Chris
