Best practices for Jenkins jobs
Using Distributed builds, version controlling the Jenkins configuration, implementing auditing of Jenkins and all the Jenkins configurations, features and plugins that we have seen in the current book were implemented in the best possible way. However, there are few critical things that were not discussed so far and need our attention. Let's see them one by one.
Avoiding scheduling all jobs to start at the same time
Multiple Jenkins jobs triggered at the same time may choke your Jenkins. To avoid this, avoid scheduling all jobs to start at the same time.
To produce even load on the system, use the symbol H. For example, using 0 0 * * * for a dozen daily jobs will cause a large bottleneck at midnight. Instead, using H H * * * would still execute each job once a day, but not all at the same time.
The H symbol can be used with a range. For example, H H(0-7) * * * means sometime between 12:00 A.M. (midnight) to 7:59 A.M. You can also use step intervals with H, with...
