-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
Jenkins ver. 1.427
Parameterized Trigger Plugin 2.12
The parameterised plugin doesn't include the "label name" in the JOB_NAME environment variable in a multi-configuration project. This was a useful feature in hudson.
The downstream project needs to know which label the parent job ran from and take a course of action based on that.
For example, when passing the job name to a downstream project, I would expect the variable to contain job-Test\label=windows and not just job-Test
Can this issue be fixed and allow the passing of the correct label in the job name?
[JENKINS-12140] Parameterized Trigger Plugin for multi-configuration project
Mee Kwan
created issue -
Mee Kwan
made changes -
| Description |
Original:
The parameterised plugin doesn't include the "label name" in the JOB_NAME environment variable in a multi-configuration project. This was a useful feature in hudson. The downstream project needs to know which label the parent job ran from and take a course of action based on that. Can this issue be fixed and allow the passing of the correct label in the job name? |
New:
The parameterised plugin doesn't include the "label name" in the JOB_NAME environment variable in a multi-configuration project. This was a useful feature in hudson. The downstream project needs to know which label the parent job ran from and take a course of action based on that. For example, when passing the job name to a downstream project, I would expect the variable to contain job-Test\label=windows and not just job-Test Can this issue be fixed and allow the passing of the correct label in the job name? |
| Resolution | New: Incomplete [ 4 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 142462 ] | New: JNJira + In-Review [ 190119 ] |
