|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
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.