-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Jenkins 2.7.4
Multijob plugin 1.22
Environment Injector Plugin 1.92.1
Matrix Project Plugin 1.7.1
Parameterized Trigger plugin 2.32
Token Macro Plugin 2.0
Conditional BuildStep 1.3.5
Maven Integration plugin 2.13
Precondition
| Job name | Input parameters | Child jobs | Input parameters of child jobs |
|---|---|---|---|
| A | a | B, C | a=$a |
| B | a | D | a=$a, b=1 |
| C | a | D | a=$a, b=2 |
| D | a, b |
See jobs B,C in attachment.
Steps
- Run A
Expected result
Job D runs twice. Each run with different parameters.
Actual result
Job D runs once. In the log of job D something like the following:
Started by upstream project "B" build number 80
originally caused by:
Started by upstream project "A" build number 7
originally caused by:
Started by user user
Started by upstream project "C" build number 80
originally caused by:
Started by upstream project "A" build number 7
originally caused by:
Started by user user
Additional info
Statistics example: 11 runs of job D instead of expected 40.
- is related to
-
JENKINS-44064 JENKINS-34789 doesn't always prevent to have a release build triggering another job
-
- Open
-
- links to
- mentioned in
-
Page Loading...