|
||||||||
|
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 tried this combination today and it was able to identify a vsphere slave node correctly:
vsphere-cloud version 2.3
build-flow plugin version 0.16
Jenkins version 1.583
Out of curiosity, I updated both plugins ... and let Jenkins stay at 1.583. That worked too. So this combination also works:
vsphere-slave plugin 2.4
build-flow plugin 0.17
Jenkins version 1.583