-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
We kick off a long running system test job as a build step in our daily build. While blocked, the daily build continues to use an executor, even though it is doing nothing. Would be nice to add an executor while the job is blocked.
I was thinking this could use a flyweight task to execute the job that's being blocked on.
This way the lifecycle of the executor is directly tied to the blocked job,
no worries that the new executor might start running a really long job.
If the job being blocked on can be run on the same node, then launch it as a
flyweight. If it can't, don't and then execute + block normally.