Hi, we have a similar issue and we use a combination of trigger cron command with "H" (if instead of * into cron syntax, you put "H" then Jenkins treats it special) >From documentation https://jenkins.io/doc/book/pipeline/syntax/ "The H symbol can be thought of as a random value over a range, but it actually is a hash of the job name, not a random function, so that the value remains stable for any given project."
But also that's is not sufficient in cases the pipeline takes more than an hour (as in our case), hence we add on top of this the usage of LockableResources and we created a resource that we lock in the stages of the pipeline we know we can't run at the same time because of constraints. https://jenkins.io/doc/pipeline/steps/lockable-resources/ So, a combination of both ... does the tricks for us and I think it should work as well for you too. Cheers, Gianluca On Wednesday, 1 April 2020 08:08:41 UTC+1, BCT Roel de Wildt wrote: > > Hello, > > > > In previous versions of Jenkins LTS there was a jenkins-cli.jar which I > used to trigger a build job. Now with the latest (2.222.1) I can’t find how > to do the build jobs on a scheduled base. Where one is shedules at 19:00, > the other on 20:30, etc… They can’t run at same time due resources limits. > What is the best option to execute a single build job in a multi branch > pipeline? > > > > Kind regards, > > Roel de Wildt > Software Engineer > > > -- 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/c96a2c92-9eb4-4e3e-9323-63c829418bc3%40googlegroups.com.
