[JIRA] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke commented on JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node 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 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.
[JIRA] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke created JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 03/Mar/15 4:56 AM Description: Steps 1) Deploy a Jenkins instance from the appropriate war, and get those 2 plugins installed. 2) Configure a test vcenter, a vsphere cloud slave instance (in my case the configuration was: boot on demand, connect via ssh launcher, shut down when idle after 10 min of idle time). 3) Tie a job to the slave and kick it off. I observe that the build simply sits in queue and never kicks off. Environment: vsphere-cloud plugin version 2.3 build-flow plugin version 0.17 Jenkins build 1.599 [Java / OS does not matter] Project: Jenkins Priority: Blocker Reporter: Parag Doke 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.
[JIRA] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions dont identify any node Change By: Parag Doke (03/Mar/15 4:57 AM) Environment: vsphere-cloudpluginversion2.3build-flowpluginversion0.17Jenkinsbuild1.599[Java version /OSdoesnotmatter] 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.
