<p>Refer to the answer here if that helps: <a href="https://stackoverflow.com/a/12472740">https://stackoverflow.com/a/12472740</a></p>
<p>There is a <code>H</code> parameter in the cron and you can also set a range in time for the <code>H</code> parameter:
<a href="https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.jelly#L47" rel="nofollow noreferrer">https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.jelly#L47</a></p>

CC BY-SA 4.0
2022-01-25T05:58:10.697Z
2022-01-25T05:58:10.697Z
kent.io
<p>This is an example of a <a href="https://en.wikipedia.org/wiki/Thundering_herd_problem" rel="nofollow noreferrer">thundering herd issue</a>.</p>
<p>A common way to deal with this issue is to sleep for a random amount of time (known as &quot;splay&quot;) at the beginning of the job.  This spreads out the load over the splay period.</p>

CC BY-SA 4.0
2022-01-19T04:49:33.617Z
2022-01-19T04:49:33.617Z
jayhendren
<p>I'd take a look at throttling your concurrent builds to reduce load:</p>
<p><a href="https://plugins.jenkins.io/throttle-concurrents/" rel="nofollow noreferrer">https://plugins.jenkins.io/throttle-concurrents/</a></p>

CC BY-SA 4.0
2022-01-19T23:40:11.600Z
Thanks for your response Casey! The tricky thing here is that we have a lot of VM capacity that we want to use, and it is only the very first part of the jobs all happening at once that causes this load (synchronizing source control). So we can handle lots of concurrent jobs, just not all of them starting at exactly the same time...
Sean
CC BY-SA 4.0
2022-01-25T23:12:11.327Z
What kind of Jenkins jobs are these?
casey vega
CC BY-SA 4.0
2022-01-18T20:15:46.350Z
2022-01-18T20:15:46.350Z
casey vega
<p>I have a daily Jenkins trigger job that sets off a bunch of CI jobs based on a cron timer. All the daily jobs are set off by this trigger job, the daily job itself doesn't do anything.</p>
<p>However, this causes a bit of a load on the infrastructure available when all these jobs start executing all at once. Is there any way to stagger the triggering of these next steps in the pipeline over a period of time?</p>

CC BY-SA 4.0
2022-01-21T11:25:32.210Z
What's the configuration of the triggering job? Is it a pipeline or freestyle and by what structure are the others triggered? Example code?
Ian W
<jenkins><jenkins-plugins><jenkinsfile>
Jenkins: Stagger triggering of next pipeline steps
Sean
# Jenkins: Stagger triggering of next pipeline steps

(Asked by: username_0 on 2022-01-14)

I have a daily Jenkins trigger job that sets off a bunch of CI jobs based on a cron timer. All the daily jobs are set off by this trigger job, the daily job itself doesn't do anything.

However, this causes a bit of a load on the infrastructure available when all these jobs start executing all at once. Is there any way to stagger the triggering of these next steps in the pipeline over a period of time?

**Tags:** jenkins, jenkins-plugins, jenkinsfile

> **Comments:**
> **username_1**: What's the configuration of the triggering job? Is it a pipeline or freestyle and by what structure are the others triggered? Example code?  

---

## 3 answers

### Answer by username_2 on 2022-01-25. Score: 1

Refer to the answer here if that helps: <https://stackoverflow.com/a/12472740>

There is a `H` parameter in the cron and you can also set a range in time for the `H` parameter:
<https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.jelly#L47>


---

### Answer by username_3 on 2022-01-19. Score: 0

This is an example of a [thundering herd issue](https://en.wikipedia.org/wiki/Thundering_herd_problem).

A common way to deal with this issue is to sleep for a random amount of time (known as "splay") at the beginning of the job. This spreads out the load over the splay period.


---

### Answer by username_4 on 2022-01-18. Score: 0

I'd take a look at throttling your concurrent builds to reduce load:

<https://plugins.jenkins.io/throttle-concurrents/>

> **Comments:**
> **username_0**: Thanks for your response Casey! The tricky thing here is that we have a lot of VM capacity that we want to use, and it is only the very first part of the jobs all happening at once that causes this load (synchronizing source control). So we can handle lots of concurrent jobs, just not all of them starting at exactly the same time...  
> **username_4**: What kind of Jenkins jobs are these?  

---

