Stop builds for a period of the day

[John Carbasse]

Hello,

Is it possible, in Jenkins or by a plugin, to forbid builds for a period (12h-14h for exemple) ?

Ideally, I look for a global parameter, I have too many jobs for set it for each.

Thanks for your time

[Stephen Connolly]

just turn on "prepare for shutdown" and turn it off again when you're done

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f3ac9d12-93e0-4d1d-a4f2-385ebbb39868%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott Evans]

Another option if you want to do it programmatically could be to use an API call via url hit to take machines offline, then put them back online.  The general format of the call should be available pretty easily with a web search, but we use something like this in a curl call when wanting to take machines offline for regular scripted maintenance:

https://<user>:<apikey>@<jenkinshost>/computer/<nodename>/toggleOffline?offlineMessage=Offline_For_Maintenance_Script

And then run it again to put the machine back online.  The only negative is that this call toggles the online/offline state, and I am not aware of a call which can be made to explicitly put a node online, or offline; just the toggle of current state.  This will take the machine offline gracefully, where any running builds will complete, but no new builds will be started.

This call could be done via a separate job on the Jenkins server itself (running on a node that doesn't get taken offline), or via any sort of external scheduling mechanism you'd like that has the ability to do a http request.

Scott

​

[Matthew...@diamond.ac.uk]

Just be aware that jobs that are scheduled to run during that period are still scheduled, and you see them waiting in the Build Queue.

 

Also, be careful if you have slaves configured “take this slave on-line when in demand, and off-line when idle”. If you have a job that Is tied to a particular slave, then when the job is put in the build queue, the slave will be taken online even if Jenkins is in “prepare for shutdown” state.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxiPpnNXtJR8GufUjH%2Bb5Qv%2B3Wfc6ATCpMJ1EAs-PX2Qg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 

[Christopher Orr]

Sounds like the Slave Squatter plugin could help:
https://wiki.jenkins-ci.org/display/JENKINS/Slave+Squatter+Plugin

> --
> 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-use...@googlegroups.com

> <mailto:jenkinsci-use...@googlegroups.com>.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/f3ac9d12-93e0-4d1d-a4f2-385ebbb39868%40googlegroups.com

> <https://groups.google.com/d/msgid/jenkinsci-users/f3ac9d12-93e0-4d1d-a4f2-385ebbb39868%40googlegroups.com?utm_medium=email&utm_source=footer>.

[John Carbasse]

Hi,
Sounds like Slave Squatter plugin is a good solution for me, I'll give it a try and if it's not what I want, I'll try with the API.
Thank you all for your help !

[Cristian Măgherușan-Stanciu]

We did it with a bit of Groovy, and we're using it for only enabling our automated continuous deployments during business hours:

import jenkins.model.*
import hudson.model.*


def jobPattern = "_Deploy_PR*"


def c= new GregorianCalendar()
def hour = c.get(Calendar.HOUR_OF_DAY)


if ((hour >= 10) && (hour < 16)) {
  def matchedJobs = Jenkins.instance.items.findAll { job ->
        job.name =~ /$jobPattern/
    }
    matchedJobs.each { job ->
       
            println "Enabling  matching job ${job.name}"
    job.enable()
          }      
    }
 else {
  def matchedJobs = Jenkins.instance.items.findAll { job ->
        job.name =~ /$jobPattern/
        }
    matchedJobs.each { job ->      
            println "Disabling matching job ${job.name}"
            job.disable()
         
    }
       
   }

[Cristian Măgherușan-Stanciu]

After pasting it, I noticed that the Groovy script could use a bit of refactoring to make it a bit cleaner:

import jenkins.model.*
import hudson.model.*

def c = new GregorianCalendar()
def hour = c.get(Calendar.HOUR_OF_DAY)

def jobPattern = "_Deploy_PR*"

def matchedJobs = Jenkins.instance.items.findAll { job -> job.name =~ /$jobPattern/ }

matchedJobs.each { job ->
  if ((hour >= 10) && (hour < 16)) {
    println "Enabling  matching job ${job.name}"
    job.enable()
  } else {