I'm searching for a more robust way of rebooting a Windows slave. I reboot our windows slaves every night as I find that they tend to play up if left too long without a restart.
Currently I try to a block builds plugin to block jobs so that the slave can be rebooted, however from time to time a job will fail because it got triggered in the narrow window between the reboot being triggered and the slave shutting down, or if the slave is particularly busy it might be hours before the reboot job can get started. I've wondered about giving up on the blocking mechanism and create a job that would run on the Slave, using Jenkins CLI to take the node offline, wait for any currently running jobs (except for itself) to complete, and then reboot the slave - I am assuming the node would automatically come back online. 1. Is this a sensible idea? 2. If so - how do I check if any jobs are running on a node? 3. Anyone have a better idea? Ta Andrew -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
