|
||||||||
|
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.
I propose to add a onReconnect() callback to the EngineListener interface in remoting. That gets called after the slave has detected that the master has recovered. The master then hooks into the new onReconnect() callback instead of onDisconnect() and restarts the slave at that point.
I've tested this on my setup with both linux and windows slaves using old slave.jar; new slave.jar with old onDisconnect() restart callback and new slave.jar with new onReconnect() restart callback. All combinations interacted properly and the fix was observed to reconnect properly with the onReconnect() hooked up in the master.