|
||||||||
|
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.
I do want jenkins to control the slave, but not all teams which have control on the salves have control on jenkins. They want to power off the slave by themself to do restorre from backup's or juts get offline to save hardware ressources fpr some time. Later they start the slave or its backup again. Jenkins shall just use if if its online , also be possible to use the vsphere features then.
At the moment the plugin tries to immideatlitly start any slave when it went offline. There is no setting to do nothing in that case. I don't want the slave to be put Offline when jenkins mean not to need it, because this salves are also used by our team, for tesing purposes beyond jenkins jobs running there.
Jenkins shall just use it if its online, don't power on or power off, but for any job istself calls it. This is not the case here, it's caused by the standard vsphere node config, where is no option "only to use if online"