Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
Description
Currently EnvironmentContributingAction is limited to AbstractBuild. A more general version should be defined which can be called from Run.getEnvironment.
Attachments
Issue Links
- is related to
-
JENKINS-32504 Make JiraEnvironmentVariableBuilder compatible with pipeline
-
- Closed
-
- relates to
-
JENKINS-42499 EnvActionImpl.ownerEnvironment cache never gets invalidated
-
- Resolved
-
-
JENKINS-29144 SimpleBuildStep to receive EnvVars
-
- Resolved
-
- links to
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-46482Use 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