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

Throttling on manually first triggered jobs of multibranch pipeline does not work

XMLWordPrintable

      Context :

      1. we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline 
        pipeline {
    agent { label ... }

    options {
        ...
        throttleJobProperty(
                categories: ['myCategory'],
                throttleEnabled: true,
                throttleOption: 'category'
        )
    }

    ...
}
      2. "myCategory" is configured properly
      3. but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
      4. so we have such jobs, where we manually triggered some job, under some "customer driven" needs

      Fact :
      Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.

        1. screenshot-1.png
          screenshot-1.png
          45 kB

          [JENKINS-72669] Throttling on manually first triggered jobs of multibranch pipeline does not work

          Pierre-Christophe created issue -
          Pierre-Christophe made changes -
          Attachment New: screenshot-1.png [ 62040 ]
          Pierre-Christophe made changes -
          Description Original: Context :
          # we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline
          {code}
          pipeline {
              agent { label ... }

              options {
                  ...
                  throttleJobProperty(
                          categories: ['myCategory'],
                          throttleEnabled: true,
                          throttleOption: 'category'
                  )
              }
          }
          {code}
          # "myCategory" is configured properly
          # but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
          # so we have such jobs, where we manually triggered some job, under some "customer driven" needs

          Fact :
          Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.           		New: Context :
          # we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline
          {code}
          pipeline {
              agent { label ... }

              options {
                  ...
                  throttleJobProperty(
                          categories: ['myCategory'],
                          throttleEnabled: true,
                          throttleOption: 'category'
                  )
              }
          }
          {code}
          # "myCategory" is configured properly
          # but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
          # so we have such jobs, where we manually triggered some job, under some "customer driven" needs !screenshot-1.png|thumbnail!

          Fact :
          Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.
          Pierre-Christophe made changes -
          Description Original: Context :
          # we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline
          {code}
          pipeline {
              agent { label ... }

              options {
                  ...
                  throttleJobProperty(
                          categories: ['myCategory'],
                          throttleEnabled: true,
                          throttleOption: 'category'
                  )
              }
          }
          {code}
          # "myCategory" is configured properly
          # but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
          # so we have such jobs, where we manually triggered some job, under some "customer driven" needs !screenshot-1.png|thumbnail!

          Fact :
          Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.           		New: *Context :*
          # we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline
          {code}
          pipeline {
              agent { label ... }

              options {
                  ...
                  throttleJobProperty(
                          categories: ['myCategory'],
                          throttleEnabled: true,
                          throttleOption: 'category'
                  )
              }
          }
          {code}
          # "myCategory" is configured properly
          # but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
          # so we have such jobs, where we manually triggered some job, under some "customer driven" needs !screenshot-1.png|thumbnail!

          *Fact :*
          Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.
          Pierre-Christophe made changes -
          Summary Original: Throttling on manually first triggered jobs do not work New: Throttling on manually first triggered jobs of multibranch pipeline does not work
          Pierre-Christophe made changes -
          Description Original: *Context :*
          # we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline
          {code}
          pipeline {
              agent { label ... }

              options {
                  ...
                  throttleJobProperty(
                          categories: ['myCategory'],
                          throttleEnabled: true,
                          throttleOption: 'category'
                  )
              }
          }
          {code}
          # "myCategory" is configured properly
          # but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
          # so we have such jobs, where we manually triggered some job, under some "customer driven" needs !screenshot-1.png|thumbnail!

          *Fact :*
          Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.           		New: *Context :*
          # we have a multibranch job, configured for discovering branches / MRs / ..., with such pipeline
          {code}
          pipeline {
              agent { label ... }

              options {
                  ...
                  throttleJobProperty(
                          categories: ['myCategory'],
                          throttleEnabled: true,
                          throttleOption: 'category'
                  )
              }

              ...
          }
          {code}
          # "myCategory" is configured properly
          # but also configured for "Suppress automatic SCM triggering" (from Branch API plugin)
          # so we have such jobs, where we manually triggered some job, under some "customer driven" needs !screenshot-1.png|thumbnail!

          *Fact :*
          Throttling works fine with respect to configuration / category, for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job.

          Daniel Beck added a comment -

          for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job

          Since the options (~ properties in non-declarative) essentially reconfigures the job every time it runs, this is likely a limitation one needs to live with. Same with build parameters, you declare them in the pipeline definition but the first build goes without.

          Daniel Beck added a comment - for jobs that have been scheduled at least once, but throttling seems to not be honored for the first run of every job in this multibranch job Since the options (~ properties in non-declarative) essentially reconfigures the job every time it runs, this is likely a limitation one needs to live with. Same with build parameters, you declare them in the pipeline definition but the first build goes without.

          Pierre-Christophe added a comment -

          ok thanks danielbeck, I think we will likely include a "forced dry-run" for the first run of such job, in order to "populate" it accordingly.

          Pierre-Christophe added a comment - ok thanks danielbeck , I think we will likely include a "forced dry-run" for the first run of such job, in order to "populate" it accordingly.

            Unassigned Unassigned
            pcbue Pierre-Christophe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: