Hi Gav, I'd certainly appreciate any help in that area. I'm guessing those are the build artifact rpms? In that case, it should not be keeping them around for more than a few days as this job is only to vet new PRs.
Do I have the ability to examine those areas? I do have it set to discard old builds more than 5 days old. I believe the artifacts should be deleted with them. -dan On Fri, Jul 20, 2018 at 6:26 AM Gav <ipv6g...@gmail.com> wrote: > Actually Dan, in the 'workspace' area of at least one node I found :- > > $JENKINS_HOME/jenkins-slave/workspace/trafficcontrol-PR_ws-space* > > The size averaged around 350MB each, not big in itself but when you > mulitply that by 6750 > such directories that make over 100GB. > > As such, I'd like to understand what these directories are, how they are > being made and > what the job configs are. > > Thanks > > > > On Fri, Jul 20, 2018 at 3:36 AM Dan Kirkwood <dang...@apache.org> wrote: > > > 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 > > > > > > > > -- > Gav... >
