-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.579
ws-cleanup 0.24
After upgrading to ws-cleanup 0.24 in order to get the asynchronous cleanup function we noticed the workspaces on our slaves getting renamed to the form of ${WORKSPACE}ws-cleanup${TIMESTAMP}. (ie, job1 would become job1_ws-cleanup_1411197183394). The expected behavior under ws-cleanup 0.24 is that these were temporary to support asynchronous processing and would be deleted. However, these directories never get removed from the slave. Over time, the slave hard drives filled up resulting in build failures.
- is blocking
-
JENKINS-53579 Asynchronous cleanup not removing renamed workspace directories on slaves
-
- Open
-
- is related to
-
-
- Resolved
-
[JENKINS-24824] Asynchronous cleanup not removing renamed workspace directories on slaves
Tom Moore
created issue -
| Link |
New:
This issue is related to |
| Workflow | Original: JNJira [ 158053 ] | New: JNJira + In-Review [ 179711 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Gregor Philp
made changes -
| Attachment | New: Screen Shot 2017-01-09 at 3.46.57 PM.png [ 35397 ] |
| Assignee | Original: vjuranek [ vjuranek ] | New: Oliver Gondža [ olivergondza ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Jakub Bochenski
made changes -
| Link | New: This issue is blocking JENKINS-53579 [ JENKINS-53579 ] |
Michaela Ervin
made changes -
| Comment |
[ My workspace directory is still getting filled with ws-cleanup directories and causing jenkins to spike all cpu cores and crash. version of plugin is 0.37 ] |