-
Bug
-
Resolution: Fixed
-
Minor
-
None
The TRIGGERED_JOB_NAMES environment variable will only ever contain one entry, always being that of the last job that was executed.
When multiple instances of the same job are executed, the environment variable TRIGGERED_BUILD_RUN_COUNT_<job name> is not updated correctly. It will always be '1'
- is related to
-
JENKINS-25675 Provide environment variables like Parameterized Trigger Plugin
-
- Resolved
-
[JENKINS-29229] Some environment variables are not updated correctly
Summary | Original: Some environmental variables are not updated correctly | New: Some environment variables are not updated correctly |
Description |
Original:
The TRIGGERED_JOB_NAMES environmental variable will only ever contain one entry, always being that of the last job that was executed. When multiple instances of the same job are executed, the environmental variable TRIGGERED_BUILD_RUN_COUNT_<job name> is not updated correctly. It will always be '1' |
New:
The TRIGGERED_JOB_NAMES environment variable will only ever contain one entry, always being that of the last job that was executed. When multiple instances of the same job are executed, the environment variable TRIGGERED_BUILD_RUN_COUNT_<job name> is not updated correctly. It will always be '1' |
Link |
New:
This issue is related to |
Assignee | New: Robert Wilson [ robwilson ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 164098 ] | New: JNJira + In-Review [ 197414 ] |
I have created a pull request containing a fix for this issue