|
||||||||
|
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 think I'm beginning to understand what you want. What you want is this:
The vSphere Plugin implements the three existing "schedules" of slave availability: always on, on/off on demand/idle, and on/off on schedule. Actually, the plugin doesn't really implement them, it just implements a way to Connect() and Disconnect() the slave. Jenkins itself - using those three schedules - will tell the slave to connect or disconnect. The slave can refuse to start if it wants, but it can't really implement its own scheduling. Jenkins does that.
Maybe you could use the "on/off on demand/idle" scheduling. Use a "In demand delay" of 0, so that Jenkins will power on the VM when needed. Then use an "Idle delay" of some very large number (I don't think -1 is infinite in this case, but worth a try...). That way, when a build is done, Jenkins will leave the slave powered on. If someone shuts the slave down, Jenkins won't restart it - unless it needs to run a job on it. And if you power the slave on when there is nothing to do, the long idle delay will prevent it from being shutdown automatically by Jenkins. Well, eventually it will be, but maybe just once a week or month.