|
||||||||
|
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 already tested the schedule "on/off on demand/idle" but even then the slave immidiately gets started if powered down, although there is no job quering it top do anything on this slave. The "very large delay" is an not to nice workaround, cause some time later it won't work, that would the first and only manually power down to the next period it happens again.
The problems is that there is no defensive startegy to make use of vmware slaves. At the moment the jenkins admin needs to disconnect the slave before any system oper can do star/stop actions on this machines beyond jenkins, e.g manitenenance or back restores...
This is i wanna have new feature for this in this issue.