• Type: Bug
• Resolution: Incomplete
• Priority: Major
• Component/s: parameterized-trigger-plugin
• Labels:

  None
• Environment:

  Jenkins ver. 1.427
  Parameterized Trigger Plugin 2.12
  

[JENKINS-12140] Parameterized Trigger Plugin for multi-configuration project

Mee Kwan created issue - 2011-12-19 06:11

Mee Kwan made changes - 2011-12-19 06:12

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?

Collapse comment: cjo9900 added a comment - 2013-02-27 17:21

cjo9900 added a comment - 2013-02-27 17:21

Is this a post-build trigger or as a buildstep.

If done as a post-build step the downsteam jobs are triggered only once from the parent matrix project so does not have access to the full paths and labels for all of the configurations. only that of the parent job variables which JOB_NAME in this case is the name of the job.

If triggered as a buildstep then the JOB_NAME environment variable should match what is available in the shell for that configuration.

Expand comment: cjo9900 added a comment - 2013-02-27 17:21

cjo9900 added a comment - 2013-02-27 17:21 Is this a post-build trigger or as a buildstep. If done as a post-build step the downsteam jobs are triggered only once from the parent matrix project so does not have access to the full paths and labels for all of the configurations. only that of the parent job variables which JOB_NAME in this case is the name of the job. If triggered as a buildstep then the JOB_NAME environment variable should match what is available in the shell for that configuration.

Collapse comment: evernat added a comment - 2014-02-26 18:58

evernat added a comment - 2014-02-26 18:58

No response from the reporter, so resolving the issue as incomplete.

Expand comment: evernat added a comment - 2014-02-26 18:58

evernat added a comment - 2014-02-26 18:58 No response from the reporter, so resolving the issue as incomplete.

evernat made changes - 2014-02-26 18:58

Resolution		New: Incomplete [ 4 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:54

Workflow

Original: JNJira [ 142462 ]

New: JNJira + In-Review [ 190119 ]