Hello, I've been using Configuration Slicing plugin[1] for a good while now. If we can agree on a discard policy in terms of days or number of builds kept it's a easy way to enforce it, at least for non-pipeline jobs.
[1] https://plugins.jenkins.io/configurationslicing On Sat, Jul 14, 2018 at 7:29 AM, Joan Touzet <woh...@apache.org> wrote: > Hi there, > > Chris over in https://issues.apache.org/jira/browse/INFRA-16768 > recommended I start a thread. > > We've been getting increasing numbers of failures on our builds > due to nodes running out of disk space. In 16768, Chris says: > > "We are getting to the point where builds are running machines out of space > faster than we can clear them out. I've cleaned up H24 a bit. We'll discuss > further, but this is going to take some cooperation amongst all builders to > start purging workspaces." > > So this is the requested thread. What do we, collectively, as > Jenkins users, need to do to clean out workspaces? I'm > fairly sure that CouchDB workspaces are pretty clean, since we > do the bulk of our builds in /tmp and try our best to clean up > after failed builds. But I am happy to admit I don't know > everything I should or shouldn't be doing. > > Chris, would a list of the "top offenders" be useful? I'm not > looking to shame anyone, but shedding a little light on the > approaches that are the biggest problem might help. > > -Joan -- Zoran Regvart
