Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40464

Support settings Quiet Period in multibranch pipeline builds

      Currently only normal pipelines, and non-pipeline job types support setting the quiet period within build triggers. Having this functionality is even more important for multi-branch pipelines because of the way reindexing after a merge occurs.

      If I want to merge a large number of branches into master, than for each merge, jenkins will trigger a rebuild of all open pull-requests. It would be great if we could merge everything quickly, and only trigger a single rebuild of each pull-request we have open.

          [JENKINS-40464] Support settings Quiet Period in multibranch pipeline builds

          Would be nice to get that feature in.

          Jean-Pierre Huynh added a comment - Would be nice to get that feature in.

          On the branch configuration page of multi-branch jobs, Quiet Period is an option, but it doesn't look like it works. The Global Quiet Period config has no effect, and there is no way to configure the setting through pipeline syntax.

          This is an important feature for reducing number of build jobs in queue.

          Ryan Hutchison added a comment - On the branch configuration page of multi-branch jobs, Quiet Period is an option, but it doesn't look like it works. The Global Quiet Period config has no effect, and there is no way to configure the setting through pipeline syntax. This is an important feature for reducing number of build jobs in queue.

          Archesh Patel added a comment -

          This feature doesn't work on single pipeline jobs as well. I am on v2.52. Any workarounds?

          Archesh Patel added a comment - This feature doesn't work on single pipeline jobs as well. I am on v2.52. Any workarounds?

          I would also find this very useful. The ability to also set the quiet period only on certain branches would also be very helpful, but while that is preferred, our workflow would work either way even if the quiet period got applied to all branches.

          Jonathan Sternberg added a comment - I would also find this very useful. The ability to also set the quiet period only on certain branches would also be very helpful, but while that is preferred, our workflow would work either way even if the quiet period got applied to all branches.

          Lenny added a comment -

          Is it supposed to work in ORG pipeline projects? This doesn't seem to work for me

          Lenny added a comment - Is it supposed to work in ORG pipeline projects? This doesn't seem to work for me

            Unassigned Unassigned
            chancez Chance Zibolski
            Votes:
            27 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated:
              Resolved: