|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
This issue is being marked a blocker because it prohibits us from picking up the vsphere-cloud plugin version available on the Jenkins update center (regular as well as stable).
However, given that we've deployed a locally built hpi, if downgrading the priority is the right way to go, please feel free to lower it.
I also set up a tiny environment (2 ESX systems on junkyard class machines and 1 vCenter running on a VM within) to test my changes. I did notice VMs being powered on and off correctly when using vSphere slave nodes. I am yet to test the build step feature (only planning to test power on and power off). Will share my observations on this issue.