Jenkins multibranch pipeline does not respect quiet period in Jenkinsfile

Question

I am using a Declarative Jenkinsfile with quiet period:

  options {
    quietPeriod(180)
    // more options
  }

Tool versions:

• Jenkins - 2.190.3
• Pipeline Multibranch Plugin - 2.21
• Pipeline Declarative Plugin - 1.4.0

Now the issue is that on GitHub SCM changes, a standalone pipeline project respects the quiet period but a multibranch pipeline project does not. It returns no error either, just triggers the build immediately on receiving webhooks.

I am aware of the open issue JENKINS-37588 on this.

Using upstream wrapper jobs with build(job: 'my-job', quietPeriod: 180) is not feasible since I have several hundred multibranch projects.

Has anyone been able to find a solution or workable alternative? Any help will be appreciated.

Answer 1

I think - unfortunately - this is currently not possible.

There is an unresolved ticket here: https://issues.jenkins-ci.org/browse/JENKINS-37588

Also there is already an open pull request for this issue: https://github.com/jenkinsci/branch-api-plugin/pull/190