TrafficControl uses docker-compose to build each component, so the disk space used is within docker's space -- not the workspace. We do attempt to clean up after each build, but would be happy to get advice to improve how we're doing it. Are there best practices others use?
thanks.. Dan Kirkwood On 2018/07/14 05:29:52, 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 >
