I deleted 3 FlexJS builds that we haven’t used in a year and a half.

On 6/10/19, 2:29 PM, "Chris Lambertus" <c...@apache.org> wrote:

    Matteo,
    
    pulsar-website cleaned up nicely. pulsar-master is still problematic - 
despite having run a few minutes ago, there are still builds dating back to 
2017 in the pulsar-master/modules/org.apache.pulsar* directories, so it also 
appears that maven module ‘discard old builds’ is not working either. I have 
not yet found any suggested solutions to this.
    
    -Chris
    
    
    
    > On Jun 10, 2019, at 11:14 AM, Chris Lambertus <c...@apache.org> 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 the 
build runs automatically (presuming it runs nighty.)
    > 
    > -Chris
    > 
    > 
    >> On Jun 10, 2019, at 11:10 AM, Matteo Merli <mme...@apache.org> wrote:
    >> 
    >> For pulsar-website-build and pulsar-master, the "discard old builds"
    >> wasn't set unfortunately. I just enabled it now. Not sure if there's a
    >> way to quickly trigger a manual cleanup.
    >> 
    >> Regarding "pulsar-pull-request": this was an old Jenkins job no longer
    >> used (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
    >> <mme...@apache.org>
    >> 
    >> On Mon, Jun 10, 2019 at 10:57 AM Chris Lambertus <c...@apache.org> wrote:
    >>> 
    >>> 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 name (mesos-packaging) please.
    >>> 
    >>> It appears that the typical ‘Discard Old Builds’ checkbox in the job 
configuration may not be working for multibranch pipeline jobs. Please refer to 
these articles for information on discarding builds in multibranch jobs:
    >>> 
    >>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.cloudbees.com%2Fhc%2Fen-us%2Farticles%2F115000237071-How-do-I-set-discard-old-builds-for-a-Multi-Branch-Pipeline-Job-&amp;data=02%7C01%7Caharui%40adobe.com%7Cd9bdd20998a542e7d09b08d6edeaad9c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636957989528414630&amp;sdata=xuGt3py408pHoBUHBf8skeMNcDcztYbFdJnbVabYVmw%3D&amp;reserved=0
    >>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-35642&amp;data=02%7C01%7Caharui%40adobe.com%7Cd9bdd20998a542e7d09b08d6edeaad9c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636957989528414630&amp;sdata=H6SJZYZYXYTfdMY5qfuIjue0Kne%2Fb0tpY3kU0yWUSYA%3D&amp;reserved=0
    >>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-34738%3FfocusedCommentId%3D263489%26page%3Dcom.atlassian.jira.plugin.system.issuetabpanels%253Acomment-tabpanel%23comment-263489&amp;data=02%7C01%7Caharui%40adobe.com%7Cd9bdd20998a542e7d09b08d6edeaad9c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636957989528424624&amp;sdata=3fwh%2FcDFdYD87fS7SMxM6YIIquomsJfKvQ%2FGRwmmOZY%3D&amp;reserved=0
    >>> 
    >>> 
    >>> 
    >>> NB: I have not fully vetted the above information, I just notice that 
many of these jobs have ‘Discard old builds’ checked, but it is clearly not 
working.
    >>> 
    >>> 
    >>> If you are unable to reduce your disk usage beyond what is listed, 
please let me know what the reasons are and we’ll see if we can find a 
solution. If you believe you’ve configured your job properly and the space 
usage is more than you expect, please comment here and we’ll take a look at 
what might be going on.
    >>> 
    >>> I cut this list off arbitrarily at 40GB workspaces and larger. There 
are many which are between 20 and 30GB which also need to be addressed, but 
these are the current top contributors to the disk space situation.
    >>> 
    >>> 
    >>> 594G    Packaging
    >>> 425G    pulsar-website-build
    >>> 274G    pulsar-master
    >>> 195G    hadoop-multibranch
    >>> 173G    HBase Nightly
    >>> 138G    HBase-Flaky-Tests
    >>> 119G    netbeans-release
    >>> 108G    Any23-trunk
    >>> 101G    netbeans-linux-experiment
    >>> 96G     Jackrabbit-Oak-Windows
    >>> 94G     HBase-Find-Flaky-Tests
    >>> 88G     PreCommit-ZOOKEEPER-github-pr-build
    >>> 74G     netbeans-windows
    >>> 71G     stanbol-0.12
    >>> 68G     Sling
    >>> 63G     Atlas-master-NoTests
    >>> 48G     FlexJS Framework (maven)
    >>> 45G     HBase-PreCommit-GitHub-PR
    >>> 42G     pulsar-pull-request
    >>> 40G     Atlas-1.0-NoTests
    >>> 
    >>> 
    >>> 
    >>> Thanks,
    >>> Chris
    >>> ASF Infra
    > 
    
    

Reply via email to