We have 2 jobs triggering from a single pull request (A and B).
Job B depends on job A, meaning job A has to finish before job B starts.
We have configured a blocking job for B to be A, but it can only block if job A is in the queue.
Some of the times job B is added to the queue faster than job A and because job A is not in the queue, job B starts (and fails).
We wanted to use a quiet period for job B to make sure job A is put to the queue before job B is considered for starting.
There are 2 places to set the job quiet time, on a global Jenkins configuration and on the Job itself.
The job object also has a getQuietPeriod() function which can be used in combination with the global settings. (if the job quiet period is not set, use the global, otherwise use the job setting)
We have 2 jobs triggering from a single pull request (
AandB). JobBdepends on jobA, meaning jobAhas to finish before jobBstarts. We have configured a blocking job forBto beA, but it can only block if jobAis in the queue.Some of the times job
Bis added to the queue faster than jobAand because jobAis not in the queue, jobBstarts (and fails).We wanted to use a quiet period for job
Bto make sure jobAis put to the queue before jobBis considered for starting. There are 2 places to set the job quiet time, on a global Jenkins configuration and on the Job itself.The plugin respects the global configuration but doesn't respect the job quiet period configuration as can be seen from this line: https://github.com/jenkinsci/ghprb-plugin/blob/4e86ed47a96a01eeaa51a479ff604252109635f6/src/main/java/org/jenkinsci/plugins/ghprb/GhprbTrigger.java#L458
The
jobobject also has agetQuietPeriod()function which can be used in combination with the global settings. (if the job quiet period is not set, use the global, otherwise use the job setting)