You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Udi Meiri (Jira)" <ji...@apache.org> on 2020/04/30 21:19:00 UTC

[jira] [Created] (BEAM-9865) Clean up jenkins workspaces for successful jobs

Udi Meiri created BEAM-9865:
-------------------------------

             Summary: Clean up jenkins workspaces for successful jobs
                 Key: BEAM-9865
                 URL: https://issues.apache.org/jira/browse/BEAM-9865
             Project: Beam
          Issue Type: Bug
          Components: build-system
            Reporter: Udi Meiri
            Assignee: Udi Meiri


Two recent bugs (and many more in the past) citing lack of disk space:
https://issues.apache.org/jira/browse/BEAM-9854
https://issues.apache.org/jira/browse/BEAM-9462

There are around 150 workspaces on each Jenkins machine: apache-beam-jenkins-1..15.
Total size:
1: 175G
7: 158G
8: 173G

The majority of jobs use a clone of the Beam read/write files under src/, which is wiped out at the start of the job (wipeOutWorkspace()), so there is really no point in keeping workspace files around after the job has completed successfully.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)