|
||||||||
|
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 don't think this is working as expected for me. I have a JOB1, which kicks off multiple concurrent JOB2s using the node label factory. I changed the JOB2 node parameter to ignore temp offline nodes, and then ran JOB1. I have 3 nodes, 2 of which only come online by demand, and one which I have marked as being temporarily offline. It looks like a job for the temp offline node is still generated, so it sits there in the queue forever. I think the node label factory needs to not generate the job in the first place?
Also, If I click "Ignore Offline Nodes" for the node label config, and run the test again, a single job is still generated that sits forever in the queue despite none of the nodes being online. A message is printed in JOB1's output "No online node for label [MYLABEL] found, triggering with original label." Not sure why that happens.
Finally, I don't know if this is related, but if I kill the jobs waiting in the queue, JOB1 sits there forever waiting for the completion of the now non-existant jobs.