-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins ver. 2.32.3, workspace cleanup plugin 1.0.5
if we run a lot of copies of the same job with workspace cleanup enabled - every next job will clean up workspaces on slaves with already running jobs. jobs are executed in parallel, so perhaps it's better to check if workspace is used currently and belongs to running job before the cleanup. it's important for us because we have ENOSPACE with cleanup disabled and many failed jobs with cleanup enabled. running job copies one-by-one is not an option for us, because it will take a lot of time.
thanks in advance
- is related to
-
JENKINS-58492 Improve robustness w.r.t. bad slave nodes
- Resolved
-
JENKINS-58493 Add NodeProperty to skip-clean-on-this-node
- Resolved
-
JENKINS-7116 Doesn't take custom workspace into account
- Closed