Same issue here.
We have one Linux master running multiple slaves, some windows, some Linux.
Linux slaves (VMWare VM) get a revert to snapshot using vmware plugin, which is not possible for windows slaves in our current environment.
To handle hanging processes and locked files, we disconnect each windows slave after 1 single build, shutdown and power on the vm.
Our problem are ever growing workspace folders, allocating far more than 80gig of disk space within about two weeks, as the async cleanup can not run and remove old workspaces due to premature disconnect and termination of the java vm.
In our case the workspace cleanup plugin can rename old workspaces successfully (* -> *ws-cleanup[1234567890]+) , but does not delete those old folders after successfully reconnecting the windows slaves.
We get no errors logged using ws-cleanup plugin version 0.28 in our build logs.
|