-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Continuous Integration
-
Environment:windb slaves
-
Tags:
This job : https://qa.nuxeo.org/jenkins/job/atimic/job/atimic_windows_slaves_cleanup/
Following Julien Carsique advice on https://github.com/nuxeo/integration-scripts/pull/22 :
Next improvement is likely to parallelize the tasks and handle busy nodes.
Because of the planed deletion, it makes sense that the node must be fully idle (even if or especially if there are multiple executors).
But the node() step reserves an executor and waits for it being assigned. So it would also work fine for the busy nodes while they have only one executor: the task will wait for being accepted.
Then it would be required to parallelize the cleanup tasks. Anyway, that is already whished if not required.
See https://support.cloudbees.com/hc/en-us/articles/230922168-Pipeline-Parallel-execution-of-tasks
Finally, in case of a node with multiple executors, you would have to find a strategy to forbid simultaneous execution of other tasks, or skip the cleanup.
- is related to
-
NXBT-2300 Enhance windb cleanup job to a pipeline way
- Resolved