-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.121.3
ws-cleanup 0.34
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 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.
- depends on
-
JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves
-
- Closed
-
- is related to
-
JENKINS-27648 Introduce directory disposal service
-
- Resolved
-
[JENKINS-53579] Asynchronous cleanup not removing renamed workspace directories on slaves
Link |
New:
This issue is related to |
Environment |
Original:
Jenkins 1.579 ws-cleanup 0.24 |
New: ws-cleanup 0.34 |
Environment | Original: ws-cleanup 0.34 |
New:
Jenkins ver. 2.121.3 ws-cleanup 0.34 |
Description | Original: 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. | New: 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 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. |
Link |
New:
This issue depends on |
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
We're experiencing same issue on Jenkins - v. 2.138.2 / WS-Cleanup plugin - v. 0.34