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

Multibranch pipeline does not allow quiet time or throttle

    XMLWordPrintable

Details

    • Improvement
    • Status: Reopened (View Workflow)
    • Major
    • Resolution: Unresolved
    • branch-api-plugin
    • None
    • Running jenkins 2.15 with pipeline-multibranch 2.8.
    • 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

            enrice Erich Mauerböck added a comment - - edited

            This still does not work with me, latest LTS jenkins 2.375.2 & branch-api-plugin 2.1051.v9985666b_f6cc

            I have the following in my declarative multibranch pipeline:

            options {
                quietPeriod 5
            }

            Unfortunately when viewing the configuration, the option is not checked, and obviously does not work either, the job is started immediately.

            yes, the job has run numerous times since the pipeline change.

            Btw. I need this only for a job triggered by some upstream job, like so:

            triggers {
                upstream 'Build Parent/develop'
            } 
            enrice Erich Mauerböck added a comment - - edited This still does not work with me, latest LTS jenkins 2.375.2 & branch-api-plugin 2.1051.v9985666b_f6cc I have the following in my declarative multibranch pipeline: options { quietPeriod 5 } Unfortunately when viewing the configuration, the option is not checked, and obviously does not work either, the job is started immediately. yes, the job has run numerous times since the pipeline change. Btw. I need this only for a job triggered by some upstream job, like so: triggers { upstream 'Build Parent/develop' }
            lprimak Lenny added a comment -

            Quiet period does not work for ORG pipeline projects

            lprimak Lenny added a comment - Quiet period does not work for ORG pipeline projects
            rajyogya015 Yogya Raj added a comment -

            Would it be possible to trigger one to one build for every commit with GitHub branch source plugin ,as i can see its triggering only one build for two PR merge

            rajyogya015 Yogya Raj added a comment - Would it be possible to trigger one to one build for every commit with GitHub branch source plugin ,as i can see its triggering only one build for two PR merge
            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.

            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.
            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. 

            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. 

            People

              Unassigned Unassigned
              bsipos Brian Sipos
              Votes:
              50 Vote for this issue
              Watchers:
              57 Start watching this issue

              Dates

                Created:
                Updated: