[JIRA] (JENKINS-16916) Create easier method to use content tokens in groovy templates

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon commented on JENKINS-16916 Create easier method to use content tokens in groovy templates Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/ScriptSandbox.java src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/templates/email-ext.groovy http://jenkins-ci.org/commit/email-ext-plugin/88aa3db61db603ff31acfa6844e15fba200bd5b7 Log: Fix JENKINS-16916 Updated ScriptContent to use better groovy setup. In default groovy script, add all content types as closures, these can be used like ${ENV(var: "BUILD_ID")} in the groovy template

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.