|
||||||||
|
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/groups/opt_out.
Just to confirm - you don't want Jenkins to power the slave on or off, just use the slave if it is online?
If this is what you want, then using the vSphere Cloud slave is NOT what you should do. You want to use the Jenkins Dumb Slave - even though the slave is a VM. The Dumb Slave has no capability to turn on or off - it relies on something other than Jenkins (human, timer based power strips, BIOS power timer controls, whatever) to turn the slave on off. If Jenkins sends a job to slave like that, it will just remain in the queue until the slave is powered on and connected.
Have you tried just using the Dumb Slave? Recommend giving that a try and seeing how that work for your situation.