[JENKINS-71636] maxConcurrentPerNode not working

[jenkins-infra-bot]

 

I have one main node and 2 slave node.

I want to limit  one task at the same time per node.

So I set maxConcurrentPerNode: 1, maxConcurrentTotal: 0

But it does not work!!

 

Here is my code

// code placeholder
options {
    throttleJobProperty categories: [], limitOneJobWithMatchingParams: false, maxConcurrentPerNode: 1, maxConcurrentTotal: 0, paramsToUseForLimit: 'Packer', throttleEnabled: true, throttleOption: 'project'
} 

 

---

Originally reported by xushunwang, imported from: maxConcurrentPerNode not working

• status: Open
• priority: Blocker
• component(s): throttle-concurrent-builds-plugin
• resolution: Unresolved
• votes: 6
• watchers: 13
• imported: 20251218-075729

Raw content of original issue

 

I have one main node and 2 slave node.

I want to limit  one task at the same time per node.

So I set maxConcurrentPerNode: 1, maxConcurrentTotal: 0

But it does not work!!

 

Here is my code

// code placeholder
options {
    throttleJobProperty categories: [], limitOneJobWithMatchingParams: false, maxConcurrentPerNode: 1, maxConcurrentTotal: 0, paramsToUseForLimit: 'Packer', throttleEnabled: true, throttleOption: 'project'
} 

 

environment

Jenkins 2.387.2<br/>
Throttle Concurrent Builds Plug-in   2.14

[jenkins-infra-bot]

levtar:

• Original comment link
• Raw content of original comment:

  We're observing the same problem with the plugin.
  Anybody may take a look at this problem?
  

We're observing the same problem with the plugin.
Anybody may take a look at this problem?

[jenkins-infra-bot]

lsjohn:

• Original comment link
• Raw content of original comment:

  I think the problem is that getThrottleJobProperty(Task task) lacks code for when task is a PlaceholderTask. Currently it only checks if task instanceof Job else returns null. Not sure how to fix this.
  

I think the problem is that getThrottleJobProperty(Task task) lacks code for when task is a PlaceholderTask. Currently it only checks if task instanceof Job else returns null. Not sure how to fix this.

[jenkins-infra-bot]

skerria:

• Original comment link
• Raw content of original comment:

  We're seeing the same issue:
  
  pipeline {
      agent { label 'autoqc' } 
      options {
          disableRestartFromStage()
          timeout(time: 1100, unit: 'SECONDS')
          timestamps()
          throttleJobProperty(
              categories: ['db_autoqc'],
              maxConcurrentPerNode: 1,
              throttleEnabled: true,
              throttleOption: 'category' 
          )
      } 
  
  Is there a work-around for this?  Is there a replacement plugin?
  

We're seeing the same issue:

pipeline {
    agent { label 'autoqc' } 
    options {
        disableRestartFromStage()
        timeout(time: 1100, unit: 'SECONDS')
        timestamps()
        throttleJobProperty(
            categories: ['db_autoqc'],
            maxConcurrentPerNode: 1,
            throttleEnabled: true,
            throttleOption: 'category' 
        )
    } 

Is there a work-around for this?  Is there a replacement plugin?

[jenkins-infra-bot]

skerria:

• Original comment link
• Raw content of original comment:

  danielbeck do you have any advice here?  I know in the past (when I worked for a different company) you were able to help us at times.
  

danielbeck do you have any advice here?  I know in the past (when I worked for a different company) you were able to help us at times.

[jenkins-infra-bot]

skerria:

• Original comment link
• Raw content of original comment:

  I get the same result using throttle():
  
  pipeline {
      agent { label 'autoqc' } 
      options {
          disableRestartFromStage()
          timeout(time: 1100, unit: 'SECONDS')
          timestamps()
          throttle(['db_autoqc'])
      } 
  
  I had a freestyle job running that was also part of db_autoqc, but this pipeline job didn't care and just started running on that same node.  Manually triggered.  The global throttle configuration in settings is the same as the throttleJobProperty configuration in my previous comment.
  

I get the same result using throttle():

pipeline {
    agent { label 'autoqc' } 
    options {
        disableRestartFromStage()
        timeout(time: 1100, unit: 'SECONDS')
        timestamps()
        throttle(['db_autoqc'])
    } 

I had a freestyle job running that was also part of db_autoqc, but this pipeline job didn't care and just started running on that same node.  Manually triggered.  The global throttle configuration in settings is the same as the throttleJobProperty configuration in my previous comment.

[jenkins-infra-bot]

minas_ti:

• Original comment link
• Raw content of original comment:

  Seeing the same problem with Jenkins 2.504.1, plugin version 2.16
  
  tried project and category configs, seeing >2 instances of this job running on the same node.
  
   
  
      agent { label 'partial'}
      options {
          timestamps()
          throttleJobProperty(
              categories: [],
              limitOneJobWithMatchingParams: false,
              maxConcurrentPerNode: 1,
              maxConcurrentTotal: 0,
              paramsToUseForLimit: 'Packer',
              throttleEnabled: true,
              throttleOption: 'project'
          )
      }
  
   
   
  
      agent { label 'partial'}
      options {
          timestamps()
          throttleJobProperty(
              categories: ['sim'],
              throttleEnabled: true,
              maxConcurrentPerNode: 2,
              throttleOption: 'category'
          )
   
  
   
  

Seeing the same problem with Jenkins 2.504.1, plugin version 2.16

tried project and category configs, seeing >2 instances of this job running on the same node.

 

    agent { label 'partial'}
    options {
        timestamps()
        throttleJobProperty(
            categories: [],
            limitOneJobWithMatchingParams: false,
            maxConcurrentPerNode: 1,
            maxConcurrentTotal: 0,
            paramsToUseForLimit: 'Packer',
            throttleEnabled: true,
            throttleOption: 'project'
        )
    }

 

 

    agent { label 'partial'}
    options {
        timestamps()
        throttleJobProperty(
            categories: ['sim'],
            throttleEnabled: true,
            maxConcurrentPerNode: 2,
            throttleOption: 'category'
        )
 

 

[jenkins-infra-bot]

[Original duplicates from Jira: JENKINS-49173]