Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Duplicate
-
Component/s: multijob-plugin
-
Environment:Jenkins version 1.651.2, Ubuntu 14.04, Multijob plugin 1.21
-
Similar Issues:
Description
In a MultiJob Project in the MultiJob Phase the Predefined parameters are no longer being passed to the phase project. In Jenkins version 1.651.1 or prior I defined env vars $PARENT_WORKSPACE and $UNIFIED_BUILD_NUMBER, using Inject Environment Variable.
Then I passed these as Predefined Parameters to the Phase project. In the Phase project, the environment variables were undefined.
After I upgraded to 1.651.2 this stopped working. Then I downgraded back to 1.651.1 and the functionality was restored.
Attachments
Issue Links
- is related to
-
-
- Resolved
-
Activity
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
Jenkins > 2.2 is also affected. This new behavior is by design. I suspect a lot of people will disable it 
An option to hide parameters on the Build With Parameters screen would be useful. It is sometimes necessary to pass parameters from one job to another, but you don't necessarily want those parameters exposed when the job is run by itself.
Ben Langton
added a comment - https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
Jenkins > 2.2 is also affected. This new behavior is by design. I suspect a lot of people will disable it
An option to hide parameters on the Build With Parameters screen would be useful. It is sometimes necessary to pass parameters from one job to another, but you don't necessarily want those parameters exposed when the job is run by itself.
Closing as a duplicate of
JENKINS-36124, which has been fixed in MultiJob 1.22