[
https://issues.apache.org/jira/browse/BEAM-9865?focusedWorklogId=462160&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-462160
]
ASF GitHub Bot logged work on BEAM-9865:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jul/20 17:09
Start Date: 22/Jul/20 17:09
Worklog Time Spent: 10m
Work Description: udim removed a comment on pull request #12326:
URL: https://github.com/apache/beam/pull/12326#issuecomment-662574679
Started seed job manually: https://ci-beam.apache.org/job/beam_SeedJob/6623/
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 462160)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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)
