|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The feature will have to come from the Jenkins core. Jenkins says Connect() - that's what the slave does, whatever it takes. And Jenkins will follow those three schedules.
There is an existing Jenkins feature: Temporary Offline. If you click on a slave, you can select "Mark this node temporarily offline". When you do that, you can then do whatever you want with the slave VM and Jenkins won't turn it on, or off, or run jobs on it. When I perform maintenance on our slaves, that's the method that I use: put the slave in temporarily offline, then do the maintenance, then bring it back online. But it does take some degree of access. That would the last thing to offer.
To have Jenkins and the slaves work EXACTLY like you describe, you would have to go into Jenkins core and add new type of scheduling.