> Is it possible that maybe Jenkins failed to cleanup these, for some
> reason? In any case, please go ahead and remove those directories.
>
> Matteo
> --
> Matteo Merli
>
>
> On Mon, Jun 10, 2019 at 2:29 PM Chris Lambertus wrote:
>>
>> Matteo,
>>
>&g
the size of your retained builds, please let me
know. I have added some additional project dev lists to the CC as I would like
to hear back from everyone on this list as to the state of their stored builds.
Thanks,
Chris
> On Jun 10, 2019, at 10:57 AM, Chris Lambertus wrote:
>
&
either. I have not yet found
any suggested solutions to this.
-Chris
> On Jun 10, 2019, at 11:14 AM, Chris Lambertus wrote:
>
> Outstanding, thanks. I believe the job cleanup runs when the next build runs.
> You could manually trigger a build to test, or we can check next time
d (since we switched to multiple smaller PR validation jobs a while
> ago). I have removed the Jenkins job. Hopefully that should take care
> of cleaning all the files.
>
>
> Thanks,
> Matteo
>
> --
> Matteo Merli
>
>
> On Mon, Jun 10, 2019 at 10:57 AM
Hello,
The jenkins master is nearly full.
The workspaces listed below need significant size reduction within 24 hours or
Infra will need to perform some manual pruning of old builds to keep the
jenkins system running. The Mesos “Packaging” job also needs to be corrected to
include the project
or "Days to keep artifacts" is left blank. Should that be set to 1 day
> too?
>
> Any other hint at things we can try to ensure builds are cleaned up
> promptly?
>
> Thanks,
> Matteo
>
> On Sun, Sep 30, 2018 at 3:57 PM Chris Lambertus wrote:
>
>> T
The main culprit on H31 appears to be pulsar ws-cleanup jobs consuming almost
40% of the disk. (The problem on H21 was something docker-related.)
This is the second project I have found (Brooklyn was the first) which is
leaving ws-cleanup directories all over the workspace and filling up the di
