-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major
-
Component/s: ws-cleanup-plugin
-
None
When using a multi-node configuration, workspace cleanup plugin doesn't clean up the left over bits of the job on the managing node.
We have a compile job that compiles on three different architectures. workspace cleanup plugin works fine on each of those three nodes, but doesn't clean up the job that launched them. We are running jenkins from tomcat, using master/slave mode, with # of executors on the jenkins master equal to 0. This causes all jobs to be launched from other nodes. The "launching/managing job" starts other multi-label (in our case multi-architecture) jobs, but it itself is never cleaned.
- is duplicated by
-
JENKINS-11192 Multi-node workspace cleanup doesn't work in master/slave mode
-
- Resolved
-
-
JENKINS-11193 Multi-node workspace cleanup doesn't work in master/slave mode
-
- Resolved
-
-
JENKINS-11194 Multi-node workspace cleanup doesn't work in master/slave mode
-
- Resolved
-
-
JENKINS-11195 Multi-node workspace cleanup doesn't work in master/slave mode
-
- Resolved
-
-
JENKINS-11196 Multi-node workspace cleanup does not work in master/slave mode
-
- Resolved
-
-
JENKINS-11197 Multi-node workspace cleanup does not work in master/slave mode
-
- Resolved
-
-
JENKINS-11198 Multi-node workspace cleanup does not work in master/slave mode
-
- Resolved
-