Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: jira-trigger-plugin
-
Labels:None
-
Environment:Jenkins 1.651.2+
Jenkins 2.3+
jira-trigger-plugin 0.4.2
-
Similar Issues:
Description
One of the fixes may well break some of your use cases in Jenkins, at least until plugins have been adapted: SECURITY-170. This change removes parameters that are not defined on a job from the build environment.
Attachments
Activity
Code changed in jenkins
User: Wisen Tanasa
Path:
src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JenkinsRunner.groovy
src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/ParameterMappingAction.groovy
http://jenkins-ci.org/commit/jira-trigger-plugin/4cf64c12f9fcbe00d54d5fcb7f8dfe9926e35f57
Log:
JENKINS-46482 Use ParametersAction instead of EnvironmentContributingAction.
Apparently EnvironmentContributingAction is not working in a pipeline job and the fix requires Jenkins core 2.76+. See JENKINS-29537.
Compare: https://github.com/jenkinsci/jira-trigger-plugin/compare/f83ef699de31...4cf64c12f9fc
Fixed to pipeline job released under 0.5.1.
CC: Michael Porter
Wisen Tanasa
added a comment - Fixed to pipeline job released under 0.5.1.
CC: Michael Porter 0.5.1 is working for me.
Michael Porter Thanks for your confirmation. You should not need the System property workaround that was needed by SECURITY-170 anymore if you are forced to use it by jira-trigger-plugin e.g. hudson.model.ParametersAction.keepUndefinedParameters or hudson.model.ParametersAction.safeParameters
Wisen Tanasa
added a comment - Michael Porter Thanks for your confirmation. You should not need the System property workaround that was needed by SECURITY-170 anymore if you are forced to use it by jira-trigger-plugin e.g. hudson.model.ParametersAction.keepUndefinedParameters or hudson.model.ParametersAction.safeParameters 
Michael Porter Thanks for letting me know, I have reopened the ticket.