[
https://issues.jenkins-ci.org/browse/JENKINS-13209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160749#comment-160749
]
SCM/JIRA link daemon commented on JENKINS-13209:
------------------------------------------------
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
src/main/resources/org/jenkinsci/plugins/scripttrigger/groovy/GroovyScriptTrigger/config.jelly
src/main/resources/org/jenkinsci/plugins/scripttrigger/groovy/GroovyScriptTrigger/help-groovySystemScript.html
http://jenkins-ci.org/commit/scripttrigger-plugin/0e8ba3d502d254f4b1a1e245e0ca1ce09258e7f8
Log:
JENKINS-13209 System Groovy script support
Add system script checkbox in configuration UI
Add log/out/job variables to groovy shell
Setup the SYSTEM user during script execution
Log envvars used for script re-writing
Log messages and stack traces if the groovy script fails
> Support System Groovy scripts
> -----------------------------
>
> Key: JENKINS-13209
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13209
> Project: Jenkins
> Issue Type: Improvement
> Components: scripttrigger
> Reporter: Eric Dalquist
> Assignee: gbois
>
> Support execution of trigger check scripts as "system" groovy scripts. These
> scripts are executed within Jenkins proper and have full access to the
> Jenkins data model and current job.
--
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
