I will try that, and for versions: Jenkins: 2.86
Email ext plugin: 2.60 Config File Provider: 2.16.4 On Thursday, December 7, 2017 at 10:44:26 AM UTC-5, slide wrote: > > Can you try enabling debug mode for email-ext (there is a checkbox in the > global config, possibly under advanced) and see if there is anything in the > logs that could help pinpoint the issue? Also, I didn't see what versions > of Jenkins, email-ext and config-file-provider you are using, can you share > that as well? > > On Wed, Dec 6, 2017 at 3:46 PM Chris T <[email protected] <javascript:>> > wrote: > >> Just to narrow down possible failure points, I did make a simple free >> style job where I added in the same command in the default content box of >> the editable email notification. And got same results as in my pipeline. >> >> >> On Wednesday, December 6, 2017 at 4:26:12 PM UTC-5, slide wrote: >> >>> Yes, that is the point. I'm not sure why it isn't working for you, I am >>> using pretty much the same thing in my setup and it works (though I am not >>> sure I have tried from a pipeline job). >>> >>> On Wed, Dec 6, 2017 at 1:28 PM Chris T <[email protected]> wrote: >>> >> I thought the point of config-file-provider plugin was so we don't have >>>> to store the template in the $JENKINS_HOME/email-templates? >>>> >>>> >>>> On Wednesday, December 6, 2017 at 3:08:43 PM UTC-5, [email protected] >>>> wrote: >>>>> >>>>> For security reason I was told, the template must reside on the master >>>>> (you can stash it and unstash it into the email template folder on the >>>>> master or you can read it and write it on master node): >>>>> >>>>> node('master') >>>>> { >>>>> writeFile([file: >>>>> "${JENKINS_HOME}/email-templates/mytempofile.jelly", text: 'template data >>>>> read from other file']); >>>>> } >>>>> emailext body: ... >>>>> >>>>> At least it was my workaround until I find something less retarded. >>>>> >>>> -- >>>> 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/38b1229b-248c-4a53-9308-45c2006213f2%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/38b1229b-248c-4a53-9308-45c2006213f2%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/78326aec-7f5e-42ba-9f59-70ddd9a0cca1%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/78326aec-7f5e-42ba-9f59-70ddd9a0cca1%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/96564b74-00c2-4bd9-b2a9-1ece5900b98f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
