Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
At the moment in order to use a content template the script must be copied into the folder $JENKINS_ROOT/email-templates, which requires filesystem access to the master.
As an alternative I want to be able to create a managed file (using the Config File Provider plugin) and then reference that file when configuring editable email notification build step.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Workflow | JNJira [ 149501 ] | JNJira + In-Review [ 193153 ] |
Code changed in jenkins
User: Alex Earl
Path:
pom.xml
src/main/java/hudson/plugins/emailext/JellyTemplateConfig.java
src/main/java/hudson/plugins/emailext/plugins/content/JellyScriptContent.java
src/main/resources/hudson/plugins/emailext/JellyTemplateConfig/JellyTemplateConfigProvider/newInstanceDetail.jelly
src/main/resources/hudson/plugins/emailext/JellyTemplateConfig/JellyTemplateConfigProvider/newInstanceDetail.properties
src/main/resources/hudson/plugins/emailext/JellyTemplateConfig/edit-config.jelly
http://jenkins-ci.org/commit/email-ext-plugin/9c8e0ac16c440293728a5f7343993857c5f47b00
Log:
Fix
JENKINS-18203Implement support for managed files as templates.