[
https://issues.jenkins-ci.org/browse/JENKINS-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160129#comment-160129
]
martinro commented on JENKINS-10985:
------------------------------------
I'm seening the same with Jenkins 1.424.2.
After installing this plugin, all nodes are disabled with the message "This
node is offline because it uses old slave.jar".
Even after updating the slave.jar on the nodes, the nodes are still disabled.
> Reenable node if version now are up to date
> -------------------------------------------
>
> Key: JENKINS-10985
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10985
> Project: Jenkins
> Issue Type: Bug
> Components: versioncolumn
> Environment: jenkins 1.430 + versioncolumn plugin 0.2
> Reporter: Conny Kreyßel
> Assignee: sogabe
>
> I have a node running via jnlp and if now the versions defer i reset
> connection i restart jnlp.
> But it does not enable the node that are offline because of version conflict.
> This should be done if i renew the node slave.jar version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
