• Type: Bug
• Resolution: Unresolved
• Priority: Blocker
• Component/s: workflow-durable-task-step-plugin
• Labels:

  None
• Environment:

  Centos7 on both master and slave. Jenkins 2.97.

1. 

   Screenshot_20180110_144412.png

   11 kB

   2018-01-10 14:07

2. 

   Screenshot_20180110_144447.png

   9 kB

   2018-01-10 14:07

3. 

   Screenshot_20180110_150544.png

   81 kB

   2018-01-10 14:06

[JENKINS-48882] Build Executor number is not consistent with EXECUTOR_NUMBER

Nuno Costa created issue - 2018-01-10 14:09

Nuno Costa made changes - 2018-01-10 14:18

Description

Original: Build Executor display number is not consistent with the number is provided by EXECUTOR_NUMBER variable. Display number should always by EXECUTOR_NUMBER+1 but it randomly shows different values. When using 4-5 executors per node (master included) seemed to be easier to replicate but not 100%. It seems to only be an issue on the display side. When using EXECUTOR_NUMBER to separate folders of maven repository artifacts, to build in parallel, the value is very important to avoid "cross contamination". We also use this variable to avoid constant download artifacts on every build, by mounting /var/lib/jenkins/.m2/repository/EXECUTOR_NUMBER inside a container. Jenkinsfile: {code:java} node('master') {     stage('on master') {         echo EXECUTOR_NUMBER         sleep 30         sh 'echo ${EXECUTOR_NUMBER}'     } } node('docker') {     stage('on slave') {         echo EXECUTOR_NUMBER         sleep 30         sh 'echo ${EXECUTOR_NUMBER}'     } } {code} Not sure if there is some way to get the Build Executor display number, so to compare, I took a screenshot from the nodes page, during the build.

New: Build Executor display number is not consistent with the number is provided by {{EXECUTOR_NUMBER}} variable.  Display number should always by {{EXECUTOR_NUMBER}}+1 but it randomly shows different values. When using 4-5 executors per node (master included) seemed to be easier to replicate but not 100%. It seems to only be an issue on the display side.  When using {{EXECUTOR_NUMBER}} to *separate* folders of maven repository artifacts, to build in parallel, *the value is very important* to avoid "cross contamination".  We also use this variable to *avoid* *constant* download artifacts on every build, by mounting {{/var/lib/jenkins/.m2/repository/EXECUTOR_NUMBER}} inside a container. Jenkinsfile: {code:java} node('master') {     stage('on master') {         echo EXECUTOR_NUMBER         sleep 30         sh 'echo ${EXECUTOR_NUMBER}'     } } node('docker') {     stage('on slave') {         echo EXECUTOR_NUMBER         sleep 30         sh 'echo ${EXECUTOR_NUMBER}'     } } {code} Not sure if there is some way to get the Build Executor display number, so to compare, I took a screenshot from the nodes page, during the build.

Andrew Bayer made changes - 2018-01-10 21:14

Component/s		New: workflow-durable-task-step-plugin [ 21715 ]
Component/s	Original: pipeline [ 21692 ]

Karl Wirth made changes - 2018-12-14 10:40

Priority

Original: Minor [ 4 ]

New: Blocker [ 1 ]

Karl Wirth made changes - 2019-12-03 17:17

Link

New: This issue is related to JENKINS-60213 [ JENKINS-60213 ]