-
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
-
JENKINS-27648 Introduce directory disposal service
-
- Resolved
-
I'm experiencing the same issue within an updated Jenkins (2.53) and ws-cleanup plugin (0.32).
I wanted to note that when I'm using the ws-cleanup into a pipeline, is working as expected. But when I'm using it into a regular Maven job it is leaving the famous directory with a timestamp (one per build!) and is filling the workspace of my slaves.
I think that this issue should be re-opened because there are more cases like this one.