Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
-
Jenkins 2.3
RHEL 7.6
Java 1.8 (OpenSDK)
Description
Changes in Jenkins 2.3 Changelog seem to break the ability to pass current generator parameters to downstream jobs.
Same jobs work with Jenkins 2.2
Attachments
Activity
Gavin Greenwood
added a comment - Hi there, We also having the issue.
Passing parameters to a child job with Jenkins 2.2 using either a free style job of a pipeline, it works as expected, perfectly (no issues).
However for any newer version 2.4 to 2.9 (current), its simple does not work.
On the current version (2.9) we tried so many things, from different/new plugin different job configs and different job types but nothing.
One thing that does work however is if the child job has the parameter defined in its own config, then it can receive the par, but this is a suitable solution (cant maintain that across all jobs). In the previous versions (<=2.2) the child didn't need the par defined, it simple received the par for the calling parent.
Please investigate this issue and assist us.
Gavin Greenwood
added a comment - Hi there, We also having the issue.
Passing parameters to a child job with Jenkins 2.2 using either a free style job of a pipeline, it works as expected, perfectly (no issues).
However for any newer version 2.4 to 2.9 (current), its simple does not work.
On the current version (2.9) we tried so many things, from different/new plugin different job configs and different job types but nothing.
One thing that does work however is if the child job has the parameter defined in its own config, then it can receive the par, but this is a suitable solution (cant maintain that across all jobs). In the previous versions (<=2.2) the child didn't need the par defined, it simple received the par for the calling parent.
Please investigate this issue and assist us. 
Tony Dunlop
added a comment - Still the same in jenkins version 2.10 and 2.11 
Reiner Wirtz
added a comment - I added the define
-Dhudson.model.ParametersAction.keepUndefinedParameters=true
in the startline of jenkins and it works fine.
Reiner Wirtz
added a comment - I added the define
-Dhudson.model.ParametersAction.keepUndefinedParameters=true
in the startline of jenkins and it works fine. Hi Reiner Wirtz, added that to my startline and it actually worked. Thanks for the share!!! 
For those who don't know, the startline can be found in the jenkins.xml file.
Gavin Greenwood
added a comment - - edited Hi Reiner Wirtz, added that to my startline and it actually worked. Thanks for the share!!!
For those who don't know, the startline can be found in the jenkins.xml file. 
Owen Lopez
added a comment - Does anyone know where I can find the startline file as of version 2.13? I don't have a jenkins.xml. I am on CentOS Linux for EC2.
Owen Lopez
added a comment - Does anyone know where I can find the startline file as of version 2.13? I don't have a jenkins.xml. I am on CentOS Linux for EC2. | Field | Original Value | New Value |
|---|---|---|
| Workflow | JNJira [ 171005 ] | JNJira + In-Review [ 184121 ] |
Zaur Salam
added a comment - vi /etc/sysconfig/jenkins 
Payel Bhattacharya
added a comment - If Jenkins is installed in windows machine. What can we do?
We are facing the issue even in v2.52 of Jenkins
Payel Bhattacharya
added a comment - If Jenkins is installed in windows machine. What can we do?
We are facing the issue even in v2.52 of Jenkins
I discovered such a problem for every jenkins parameter in 2.3, 2.4 and 2.5.
No Parameter can be evaluated in the started jenkins child job.