|
||||||||
|
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.
If you don't want Jenkins to control the slave as if it where a VM - allowing power-on, power-off, revert on demand - then I would suggest that you don't need the slave to be a vSphere Cloud slave, but just a normal dumb slave. Jenkins lets you create those and leaves the turning on, turning off to you.
The intent behind the vSphere Cloud slaves is that Jenkins can control the slave more closely. It sounds like you don't want it to have that degree of control. The dumb slave would probably work better for you.