[ https://issues.apache.org/jira/browse/HBASE-24936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182706#comment-17182706 ]
Sean Busbey commented on HBASE-24936: ------------------------------------- wishlist: add a stage that can run on master and abort our builds that use a lot of space when freespace is low. that would let the lighter weight builds keep working. > review Jenkins build artifacts > ------------------------------ > > Key: HBASE-24936 > URL: https://issues.apache.org/jira/browse/HBASE-24936 > Project: HBase > Issue Type: Task > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Critical > > Post move to the ci-hadoop build servers we are now the biggest user of > space. That is not a problem in and of itself, but the master node has run > out of disk space twice now. As of this snapshot we are using 125GB of > storage and the next largest project is only using 20GB. > https://paste.apache.org/kyrds > We should review our builds for any issues and come up with expectations for > what our steady-state disk usage should look like > * we are supposed to compress any test logs (usually this gets us 90-99% > space savings) > * we are supposed to clean up workspaces when jobs are done > * we are supposed to keep a fixed window of prior builds (either by days or > number of runs) > If all of our jobs are currently following these guidelines, another > possibility is to push the artifacts we need over to > [nightlies.a.o|https://nightlies.apache.org/authoring.html]. Barring that, we > should formally request asf infra set up [a plugin for storing artifact on > s3|https://plugins.jenkins.io/artifact-manager-s3/]. -- This message was sent by Atlassian Jira (v8.3.4#803005)