|
||||||||
|
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/d/optout.
With my current plugin updates, the problem has gone away, except in this use case:
1. Quiet Jenkins (announce "shut down")
2. Wait for all running builds to complete on all nodes
3. Queue a build of the matrix job
4. Cancel shutdown
5. Job begins building on all nodes except the one running the flyweight launcher task; build for that node remains queued in the deadlock condition.
So far it works to exchange steps 3 & 4, and hope nothing else gets queued to run between them.