[JIRA] (JENKINS-40303) Jenkinsfile node() command ignores maxConcurrentPerNode

2016-12-07 Thread e...@omikron.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eduard Wirch updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40303  
 
 
  Jenkinsfile node() command ignores maxConcurrentPerNode   
 

  
 
 
 
 

 
Change By: 
 Eduard Wirch  
 

  
 
 
 
 

 
 This is roughly the {{Jenkinsfile}} of our pipeline build:{code}properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '', numToKeepStr: '10')),[$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: false, maxConcurrentPerNode: 1, maxConcurrentTotal: 4, paramsToUseForLimit: '', throttleEnabled: true, throttleOption: 'project'],pipelineTriggers([])])node('ff') {}{code}Note, that {{maxConcurrentPerNode}} is 1.  "ff" is a node group, not the name of a single node.  This morning I found two builds for the same job started at the same time on the same node:{code}#34: 08:21:35 Running on jenkins04 in /var/lib/jenkins/workspace/r-Framework-Pipeline_master-ANZFTZAHSF7Z3GZCE4P4EWA2KLDAN62QSMCCUDZ4BRCFVS5MIHAA#35: 08:21:35 Running on jenkins04 in /var/lib/jenkins/workspace/r-Framework-Pipeline_master-ANZFTZAHSF7Z3GZCE4P4EWA2KLDAN62QSMCCUDZ4BRCFVS5MIHAA@2{code}You see nicely by the {{@}} sign in the workspace path that both builds indeed started on the same node.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] (JENKINS-40303) Jenkinsfile node() command ignores maxConcurrentPerNode

2016-12-07 Thread e...@omikron.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eduard Wirch created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40303  
 
 
  Jenkinsfile node() command ignores maxConcurrentPerNode   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Dec/08 7:50 AM  
 
 
Environment: 
 Jenkins ver. 2.8  
 
 
Labels: 
 pipeline regression  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Eduard Wirch  
 

  
 
 
 
 

 
 This is roughly the Jenkinsfile of our pipeline build: 

 

properties([
buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '', numToKeepStr: '10')),
[$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: false, maxConcurrentPerNode: 1, maxConcurrentTotal: 4, paramsToUseForLimit: '', throttleEnabled: true, throttleOption: 'project'],
pipelineTriggers([])
])

node('ff') {
}
 

 Note, that maxConcurrentPerNode is 1. This morning I found two builds for the same job started at the same time on the same node: 

 

#34: 08:21:35 Running on jenkins04 in /var/lib/jenkins/workspace/r-Framework-Pipeline_master-ANZFTZAHSF7Z3GZCE4P4EWA2KLDAN62QSMCCUDZ4BRCFVS5MIHAA
#35: 08:21:35 Running on jenkins04 in