[
https://issues.jenkins-ci.org/browse/JENKINS-13208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160748#comment-160748
]
SCM/JIRA link daemon commented on JENKINS-13208:
------------------------------------------------
Code changed in jenkins
User: Eric Dalquist
Path:
src/main/java/org/jenkinsci/plugins/scripttrigger/groovy/GroovyScriptTrigger.java
src/main/java/org/jenkinsci/plugins/scripttrigger/groovy/GroovyScriptTriggerExecutor.java
http://jenkins-ci.org/commit/scripttrigger-plugin/726ad01dc8d9603f7e8c6c1b93c99cc8e7138332
Log:
JENKINS-13208 Use EnvVarsResolver for groovy scripts
Get the environment variables for groovy scripts via the EnvVarsResolver
> Use EnvVarsResolver for Groovy scripts
> --------------------------------------
>
> Key: JENKINS-13208
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13208
> Project: Jenkins
> Issue Type: Improvement
> Components: scripttrigger
> Reporter: Eric Dalquist
> Assignee: gbois
>
> Currently groovy scripts only have access to the node environment variables
> unlike shell scripts which use EnvVarsResolver and have access to the job
> variables as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
