Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
Description
When creating a multi-configuration job, parameters are not passed as environment variables.
Screenshot of configuration: http://i.imgur.com/aPmXiXT.png
Running, as the execute command 'set' (which dumps all environment variables), neither of those are visible (see attached output)
When trying to view the Params of the submitted job, the panel is blank: http://i.imgur.com/DcwOR5a.png
Jenkins version is reported as 2.4, installed via RPM from http://pkg.jenkins-ci.org/redhat
This appears to be a regression with SECURITY-170 - Adding -Dhudson.model.ParametersAction.keepUndefinedParameters=true to JENKINS_JAVA_OPTIONS in /etc/sysconfig/jenkins then make the parameters visible again.
Note that these Params are explicitly defined in the job, and should not be getting removed.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
Activity
Rob Thomas
created issue -
Rob Thomas
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
When creating a multi-configuration job, parameters are not passed as environment variables. Screenshot of configuration: http://i.imgur.com/aPmXiXT.png Running, as the execute command 'set' (which dumps all environment variables), neither of those are visible (see attached output) When trying to view the Params of the submitted job, the panel is blank: http://i.imgur.com/DcwOR5a.png |
When creating a multi-configuration job, parameters are not passed as environment variables. Screenshot of configuration: http://i.imgur.com/aPmXiXT.png Running, as the execute command 'set' (which dumps all environment variables), neither of those are visible (see attached output) When trying to view the Params of the submitted job, the panel is blank: http://i.imgur.com/DcwOR5a.png Jenkins version is reported as 2.4, installed via RPM from http://pkg.jenkins-ci.org/redhat |
Rob Thomas
made changes -
| Attachment | support_2016-05-17_01.36.13.zip [ 32730 ] |
Rob Thomas
made changes -
| Description |
When creating a multi-configuration job, parameters are not passed as environment variables. Screenshot of configuration: http://i.imgur.com/aPmXiXT.png Running, as the execute command 'set' (which dumps all environment variables), neither of those are visible (see attached output) When trying to view the Params of the submitted job, the panel is blank: http://i.imgur.com/DcwOR5a.png Jenkins version is reported as 2.4, installed via RPM from http://pkg.jenkins-ci.org/redhat |
When creating a multi-configuration job, parameters are not passed as environment variables. Screenshot of configuration: http://i.imgur.com/aPmXiXT.png Running, as the execute command 'set' (which dumps all environment variables), neither of those are visible (see attached output) When trying to view the Params of the submitted job, the panel is blank: http://i.imgur.com/DcwOR5a.png Jenkins version is reported as 2.4, installed via RPM from http://pkg.jenkins-ci.org/redhat This appears to be a regression with SECURITY-170 - Adding -Dhudson.model.ParametersAction.keepUndefinedParameters=true to JENKINS_JAVA_OPTIONS in /etc/sysconfig/jenkins then make the parameters visible again. Note that these Params are *explicitly defined* in the job, and should not be getting removed. |
| Labels | Parameterized |
| Link |
This issue duplicates |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 171064 ] | JNJira + In-Review [ 199024 ] |