|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm afraid I am infrequent on updates, and have always have issues with my nodes in one way or another, so it's hard to pinpoint exactly when this started. I would say at least since 1.565, but probably before then too.
When I say that the node still claims it is connected, I am referring to the console log that is displayed on the node itself. Jenkins still sees the node as offline and says "The current peer is reconnecting." in the node status.