Precisely what we do. Every morning we run a scheduled job to grab and install our master list of Jenkins plugins and then trigger a safeRestart via a System Groovy build step. Works like a charm and hasn't failed us in over six months.
One thing to watch out for: if your developers have a rogue job, perhaps one with a broken, never-ending test, then you might come in Monday morning to a Jenkins instance still stuck in quiet mode with a full build queue. The queue will persist a restart but it's not good, especially if other teams are relying on Jenkins to deploy to regions or perform critical tests over the weekend. If a team is guilty of preventing a restart then we move their job(s) to a purgatory until they fix the problem. You could also use the build timeout plugin I guess. On Thursday, February 27, 2014 5:39:45 AM UTC-5, Daniel Beck wrote: > > If you use the Groovy plugin, you could create a job that performs > safeRestart in a System Groovy build step with > 'jenkins.model.Jenkins.instance.safeRestart()'. Schedule as you would any > other job. > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
