Hi,
until very recently I was able to schedule the execution of jobs via the http api making use of the delay parameter, as described in https://stackoverflow.com/a/16573716/543321 My use case is to schedule a job to do some maintenance overnight, and I trigger it manually whenever it is needed with a frequency of ~once per month. From a python script, and using the Jenkins module, I compute the delay needed for the job to run at a specific time in the next 24h like “$ ./admin.py schedule jenkins-pipeline 04:30”. This worked fine until today, when the job started building immediately after being queued, as if the delay parameter was ignored. I’m sure the api call was made correctly. Anyone knows if there was any update removing this behavior? Is there any alternative method to achieve the same goal? Thanks! Roger -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cc4c7620-91e6-4f2f-a990-08d178d12ef7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
