I wonder if you could use: https://wiki.jenkins-ci.org/display/JENKINS/Schedule+Build+Plugin with another job, that fires up and checks if it should run as a pre build step, and then runs (downide is that it will run, even if there isn't work to do from upstream, so perhaps there is a better way).
I feel your pain re timezones (I am timezone challenged myself!). On Thursday, September 17, 2015 at 1:31:19 AM UTC+10, nfwlpw wrote: > > Here's my dilemma. > > I have a job in my pipeline that sits off the main path, but they do > depend on part of the main pipeline (parameters and artifacts). The team > that owns this job is in a different timezone so they want the job to start > at a time convenient for them. > > Is there a way I can have this step stay in the pipeline, but wait until a > certain time to fire off? I thought adding a quiet period but start time > won't be exact also makes it annoying if I want to run just that step > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/fa71b5b0-bff1-4281-83f6-68226ff15c12%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
