Improving Jenkins Pipeline Speeds By Lowering Quiet Periods

Posted on Thu 12 June 2014 in Uncategorized

Disclaimer: If you've ever looked at the "quiet period" feature before, this blog post will be extremely boring to you.

So today was the first time I took a real look at the quiet period setting available to Jenkins jobs.

I had created a pipeline using the build flow plugin consisting of two jobs (three if you include the actual pipeline). According to the build graph view, all of the individual jobs took only 2.4 seconds to run, combined. Yet, the pipeline took a whopping 10 whole seconds to run. Here's a screenshot:

pipeline view - before

After a bit of snooping around I stumbled upon the single most useless feature to ever get included in any application (imvho): "quiet period". You can find that on your job configuration page, under "Advanced Project Options".

The quiet period feature basically prevents a job from running for x seconds after it's been scheduled. This would be useful in a variety of situations, according to some credible sources. The default value is set to 5. 5 whole seconds. Per job. That you're never getting back.

Here's my pipeline after I'd set the quiet period to 0 seconds:

pipeline view - after

You're welcome. Feel free to tell me why I did a bad thing.