nced) 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 >
> wrote:
>
&
, 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 >
> wrote:
>
>> I thought t
The plugins were install a while ago, and have been restarted (at least a
few times) since then.
On Wednesday, December 6, 2017 at 5:02:04 PM UTC-5, Daniel Beck wrote:
>
>
> > On 6. Dec 2017, at 19:42, Chris T >
> wrote:
> >
> > So yes I do have config-
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, jer...@bodycad.com
wrote:
>
> For security reason I was told, the template must reside on the master
> (you can
I originally had the template name without ".jelly", but got same (not
working) results.
On Wednesday, December 6, 2017 at 3:01:42 PM UTC-5, slide wrote:
>
> Just for kicks, can you try removing .jelly from the name of the template?
>
> On Wed, Dec 6, 2017 at 12:
And how is "config-file-provider" used?
In the emailext:
body: '${JELLY_SCRIPT, template="managed:"}',
or
body: '${SCRIPT, template="managed:"}',
But this isn't working for me.
On Sunday, March 1, 2015 at 4:16:19 PM UTC-5, slide wrote:
>
> The other option is if you install the config-file-pro
