[
https://issues.jenkins-ci.org/browse/JENKINS-13209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160751#comment-160751
]
SCM/JIRA link daemon commented on JENKINS-13209:
------------------------------------------------
Code changed in jenkins
User: Gregory Boissinot
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/2f6250443add42f6c3ccd5d2ec34ee70abb612f3
Log:
Merge pull request #2 from edalquist/JENKINS-13209
JENKINS-13209 System Groovy script support
Compare:
https://github.com/jenkinsci/scripttrigger-plugin/compare/14b1178...2f62504
> 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
