Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: email-ext-plugin
-
Labels:
-
Similar Issues:
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
Added information on the managed: syntax to the help for the SCRIPT and JELLY_SCRIPT tokens.
Hello guys. Thank you for this feature. However, I am not able to get the "managed:" feature work. It simply cannot find the file (even though it is there). Can you point me to some working example so I can rule out I'm doing something wrong, please?
Martin Cimbalek
added a comment - - edited Hello guys. Thank you for this feature. However, I am not able to get the "managed:" feature work. It simply cannot find the file (even though it is there). Can you point me to some working example so I can rule out I'm doing something wrong, please? Martin Cimbalek probably want to ask on the Jenkins Users mailing list. The feature has been in place for a long time (7 years) and has tests. So, asking your question on the mailing list would be best. I no longer maintain this plugin, but someone on the mailing list may be able to help.
Will do, thanks!
Martin Cimbalek
added a comment - Will do, thanks! 
Good idea, I'll do that.