-
Bug
-
Resolution: Duplicate
-
Minor
-
Jenkins version 1.651.2, Ubuntu 14.04, Multijob plugin 1.21
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.
- is related to
-
-
- Resolved
-
[JENKINS-34864] MultiJob predefined parameters no longer passed to phase project
M Chon
made changes -
| Component/s | New: envinject-plugin [ 15893 ] |
M Chon
made changes -
| Component/s | New: core [ 15593 ] |
M Chon
made changes -
| Attachment | New: Screen Shot 2016-05-16 at 10.35.55 AM.png [ 32726 ] | |
| Labels | Original: jenkins plugin | New: envinject jenkins multi-job plugin |
M Chon
made changes -
| Attachment | Original: Screen Shot 2016-05-16 at 10.35.55 AM.png [ 32726 ] |
M Chon
made changes -
| Attachment | New: Screen Shot 2016-05-16 at 10.35.55 AM.png [ 32727 ] |
M Chon
made changes -
| Attachment | New: Multijob Parameterized Trigger Predefined Parameters.PNG [ 32728 ] | |
| Labels | Original: envinject jenkins multi-job plugin | New: envinject jenkins multi-job parameterized-trigger plugin |
M Chon
made changes -
| Attachment | Original: Screen Shot 2016-05-16 at 10.35.55 AM.png [ 32727 ] |
M Chon
made changes -
| Description | Original: 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 could pass the $WORKSPACE and $BUILD_NUMBER to the phase project, and after I upgraded to 1.651.2 this stopped working. Then I downgraded back to 1.651.1 and the functionality was restored. |
New:
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. |
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.