Hi,
is there a change into email-ext lately (I was into Jenkins 2.51 and 
email-ext 2.56, now updated to Jenkins 2.54 with 2.57.2)  that could 
prevent email-ext to fetch template into the node with an absolute path? My 
outgoing email used to work now I receive this into my email body:

Jelly file [c:/Jenkins/workspace/CAD_CPP/CAD_CPP_ContinuousBuild@tmp/
email_template_file.jelly] was not found in $JENKINS_HOME/email-templates.

The file was present on the node is there a way to fix this or an approval 
switch to enable?

I'm guessing this got broke into the 2.57 or 2.57.2 release:
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin

P.S.: Sometime I wish there was a non secure global switch and we could 
accept the server run into a secure local network and don't have to mess 
around with all the security non sense and modification that always broke 
the build machine at every Jenkins update. I still have the slave hang 
during the whole building phase, there's still many bugs report for this 
(over 2 years, and this important bug don't get fix, then we see 'security' 
features that remove working use case all the time). Maintaining Jenkins is 
more time consuming then maintaining our code base. Maybe I should stop 
update it, but I still hope the Windows slave hanging will be fix one day, 
if that day come around and I get it to work, I might highly tempted to 
stop updating.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6f602780-ff11-4110-8329-56faf95895c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to