Anybody know if this is part of another security risk or just a bug of
emailext command into pipeline?
I was creating a template on teh fly by concat of wanted sections by my
pipeline steps results
def email_template_file = pwd([tmp: true]) + "\\email_template_file.jelly";
writeFile([file: email_template_file, text: email_info['body']]);
Sending the email was working before.
emailext body: '${JELLY_SCRIPT,template="' + email_template_file.replaceAll(
'[\\\\]','/') + '"}'
This used to work now it seem like email-ext doesn't check into the current
node path, but only into the $JENKINS_HOME/email-templates!
Since I create the template by concat part, I was keeping it into the node
tmp. This is particulary annoying since many node can try to do the same,
so I will have to copy a file back on the master with a guid name and send
the email then delete that file back.
Any help would be appreciate (or plugin fix too that can handle both
absolute path again and the relative one for those who have a static
template).
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/9259d821-064f-4b8c-a3c7-a72c11f7a7bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
