[
https://issues.apache.org/jira/browse/BEAM-9865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-9865:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved
but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click
the "Resolve" button (you can do this even for closed issues) and set the
Resolution field to the right value.
> 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
> Priority: P3
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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)
