[
https://issues.apache.org/jira/browse/BEAM-9865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148840#comment-17148840
]
Beam JIRA Bot commented on BEAM-9865:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
