[
https://issues.apache.org/jira/browse/BEAM-9865?focusedWorklogId=462718&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-462718
]
ASF GitHub Bot logged work on BEAM-9865:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/20 21:47
Start Date: 23/Jul/20 21:47
Worklog Time Spent: 10m
Work Description: udim commented on pull request #12326:
URL: https://github.com/apache/beam/pull/12326#issuecomment-663248519
> With that change, all workspaces will be always cleared, just after the
build. Isn't that a problem in case of some possible investigations in the
future?
>
> We may implement something like
[this](https://blog.clairvoyantsoft.com/jenkins-cleanup-workspace-reduce-disk-usage-18310097d3ef),
WDYT?
I wasn't aware that you were working on this bug. The ws-cleanup plugin can
be configured not to clean up after failures. However, I don't recall the last
time I needed to ssh into a workspace because I needed to look at the files.
----------------------------------------------------------------
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: 462718)
Time Spent: 2h 20m (was: 2h 10m)
> 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: 2h 20m
> 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)
