[JIRA] [core] (JENKINS-22758) Jenkins >=1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)

[cbos...@gmail.com (JIRA)]

Cees Bos edited a comment on JENKINS-22758 Jenkins >=1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin) It looks like not only an issue with swarm plugin. Today we did an update to 1.560 (from 1.554). We noticed 2 things: We have a regular restart of the JNLP slaves with a Groovy script executed on the slave itself as soon as the executor is free. Each slave has only 1 executed. There are long running jobs active on the JNLP saves. So normally it waits till the job is completed, then the next item gets executed. But now the restart task got executed right away, and broke the running job. The machine got restarted and then tried to connect again to Jenkins, that fails. We have a number of jnlp slaves, but we don't get them connected anymore. >From the perspective of the slave it shows 'connected', but Jenkins master shows it as still unconnected. We have a Jenkins master on Linux and mix of all kind of slaves. In Jenkins you can click on 'Log' for a node, then there is: JNLP agent connected from /10.1.29.228 But the UI still shows it as offline.

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.