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

Multibranch pipeline does not allow quiet time or throttle

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: branch-api-plugin
    • Labels:
      None
    • Environment:
      Running jenkins 2.15 with pipeline-multibranch 2.8.
    • Similar Issues:
    • Released As:
      branch-api-plugin-2.6.0

      Description

      Currently, for an individual pipeline job I can set a quiet time to avoid one-for-one commit-to-build ratio when there are many commits in a short time. I like to use the multibranch plugin to allow branch automation, but there does not appear to be a way for a multibranch config (either the meta-job itself or from within a Jenkinsfile) to define a quiet time or some other ability to throttle job runs.

        Attachments

          Issue Links

            Activity

            Hide
            deiwin Deiwin Sarjas added a comment -

            Would it be possible possible to configure this once for the entire GitHub Organization? I read the thread and the PRs but I don't see how one could do that.

            Show
            deiwin Deiwin Sarjas added a comment - Would it be possible possible to configure this once for the entire GitHub Organization ? I read the thread and the PRs but I don't see how one could do that.
            Hide
            hemp Chris Hemp added a comment -

            ^ Related to Github - With dependabot being enabled for a repo to update dependencies, it can be common to have a few PRs merge at once.  This quiet period would be helpful to have in those situations. 

            Show
            hemp Chris Hemp added a comment - ^ Related to Github - With dependabot being enabled for a repo to update dependencies, it can be common to have a few PRs merge at once.  This quiet period would be helpful to have in those situations. 
            Hide
            brianjmurrell Brian J Murrell added a comment -

            This would be useful in GitHub if one has a GitHub Action that pushes a commit to one's PR – to prevent the the PR from building prior to the GH Actions adding the new commit.

             

            Show
            brianjmurrell Brian J Murrell added a comment - This would be useful in GitHub if one has a GitHub Action that pushes a commit to one's PR – to prevent the the PR from building prior to the GH Actions adding the new commit.  
            Hide
            jdcskillet Joe Cavanaugh added a comment - - edited

            I know I got this working when I was using Polling on the Multibranch pipeline. The quietPeriod was respected... however, when I moved to webhooks to kick off the pipeline through Bitbucket the quietPeriod(60) is no longer respected. I have gotten multiple complaints from Developers on this one as well.

                options {
                     buildDiscarder logRotator(numToKeepStr: '5')
                     disableConcurrentBuilds()
                     disableResume()
                     quietPeriod 60
                     timeout(time: 3, unit: 'HOURS')
                     skipStagesAfterUnstable()
                     parallelsAlwaysFailFast()
                 }
            Show
            jdcskillet Joe Cavanaugh added a comment - - edited I know I got this working when I was using Polling on the Multibranch pipeline. The quietPeriod was respected... however, when I moved to webhooks to kick off the pipeline through Bitbucket the quietPeriod(60) is no longer respected. I have gotten multiple complaints from Developers on this one as well.     options {         buildDiscarder logRotator(numToKeepStr:  '5' )         disableConcurrentBuilds()         disableResume()         quietPeriod 60         timeout(time: 3, unit:  'HOURS' )         skipStagesAfterUnstable()         parallelsAlwaysFailFast()     }
            Hide
            addib Dibakar Aditya added a comment - - edited

            vincenzo cerbone, I have tried both the Declarative and Scripted approach that you suggested on Jenkins 2.204.1 with the latest version of plugins. Though I can see the quiet period being set in the job configuration page of the branch, multibranch still chooses to ignore it.

            Show
            addib Dibakar Aditya added a comment - - edited vincenzo cerbone , I have tried both the Declarative and Scripted approach that you suggested on Jenkins 2.204.1 with the latest version of plugins. Though I can see the quiet period being set in the job configuration page of the branch, multibranch still chooses to ignore it.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bsipos Brian Sipos
              Votes:
              49 Vote for this issue
              Watchers:
              54 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: