[JENKINS-7557] Overlapping parameterized builds gets confused on downstream jobs

We run job 'ONE' that calls parameterized jobs "A","B","C" and "D" with a join job

We have another job 'TWO' that also calls jobs "A" and "B" with a different join job. (Maybe not the best idea, but it seemed a good one at the time.)

Let's say job TWO is started and triggers job A (build 129) and job B (build 122)

Before job A and job B are finished, someone starts job ONE.

Job ONE starts job A (build 130) and job B (build 123) correctly, along with jobs C and D.

In the log of job ONE it reports it started job A #129 and job B #122 instead of the correct job numbers. (Now I haven't tried to figure out if "join" gets confused by all of this, but the possibility is there.)

Here are some cut and paste from the logs:

[cwrt-trunk-WST-MMO-try] Build 17: (JOB TWO)

Triggering a new build of cwrt-trunk-HARVEY-MMO-arm-try #129

Triggering a new build of cwrt-trunk-HARVEY-MMO-i486-try #122

[cwrt-trunk-WST-all-try] Build 982: (JOB ONE)

Triggering a new build of cwrt-trunk-HARVEY-MMO-arm-try #129

Triggering a new build of cwrt-trunk-HARVEY-MMO-i486-try #122

Triggering a new build of cwrt-trunk-linux-LNX-try #227

Triggering a new build of cwrt-trunk-tb101_BANGER-Win-WST-try #152

-----------------

---
Originally reported by markjwolff, imported from: Overlapping parameterized builds gets confused on downstream jobs

• assignee: huybrechts
  
• status: Open
  
• priority: Major
  
• component(s): parameterized-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 2025-12-07
  

Raw content of original issue

We run job 'ONE' that calls parameterized jobs "A","B","C" and "D" with a join job

We have another job 'TWO' that also calls jobs "A" and "B" with a different join job. (Maybe not the best idea, but it seemed a good one at the time.)


Let's say job TWO is started and triggers job A (build 129) and job B (build 122)

Before job A and job B are finished, someone starts job ONE.


Job ONE starts job A (build 130) and job B (build 123) correctly, along with jobs C and D.

In the log of job ONE it reports it started job A #129 and job B #122 instead of the correct job numbers.  (Now I haven't tried to figure out if "join" gets confused by all of this, but the possibility is there.)


Here are some cut and paste from the logs:

[cwrt-trunk-WST-MMO-try] Build 17: (JOB TWO)

Triggering a new build of cwrt-trunk-HARVEY-MMO-arm-try #129

Triggering a new build of cwrt-trunk-HARVEY-MMO-i486-try #122


[cwrt-trunk-WST-all-try] Build 982: (JOB ONE)

Triggering a new build of cwrt-trunk-HARVEY-MMO-arm-try #129  

Triggering a new build of cwrt-trunk-HARVEY-MMO-i486-try #122

Triggering a new build of cwrt-trunk-linux-LNX-try #227

Triggering a new build of cwrt-trunk-tb101_BANGER-Win-WST-try #152

-----------------

• environment: Hudson 1.372, ext-email, join, other basic plug-ins