> On 18. Jun 2017, at 07:43, Seb M wrote:
>
> So this does not really seam to work? Or is there some error in my syntax?
Tri triple-single-quoted strings or escaping the $ -- right now, it's looking
for a DSL variable "CHANGES" as it evaluates the ${CHANGES, …} in the DSL.
--
You received th
To pick this up again, i also tried to get this to work and ran into some
issues:
emailext (
subject: "subject",
body: """STARTED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':
${CHANGES, showPaths=true}
Check console output at "${env.JOB_NAME}
[${env.BUILD_NUMBER}],
Into pipeline they are working to certain extent, but you have to take
special care when declaring the usage of the body (it does not support
windows \ into the path, convert to unix path type):
emailext body: '${JELLY_SCRIPT,template="/path/to/templatefile.template"}',
subject: 'subject', to:
What did you try, and what was the result?
On Tue, May 23, 2017 at 6:12 AM Doron Shai wrote:
> Do you know how i can use the CHANGES script token ? It does not see to be
> possible according to what I tried
>
> On Tue, May 23, 2017 at 4:10 PM, Slide wrote:
>
>> Many macros should work fine
Do you know how i can use the CHANGES script token ? It does not see to be
possible according to what I tried
On Tue, May 23, 2017 at 4:10 PM, Slide wrote:
> Many macros should work fine by putting them in the body or subject fields
> of the pipeline. SCRIPT specifically uses some things fro
Many macros should work fine by putting them in the body or subject fields
of the pipeline. SCRIPT specifically uses some things from AbstractBuild,
which a pipeline job is not, so that is why SCRIPT can't be used. It would
need to be updated to support pipeline jobs as well.
On Tue, May 23, 2017
Any update about that?
I found it really missing. can not use templates / can not use other
token macros such CHANGES...
I think that the whole JenkinsFile concept is great but still not mature
for real use...
On Thursday, April 21, 2016 at 5:21:52 PM UTC+3, slide wrote:
>
> The biggest
Hi, any updates on this?
Regards,
Andrew
On Thursday, April 21, 2016 at 4:21:52 PM UTC+2, slide wrote:
>
> The biggest hurdle at this point is that email-ext uses token macro for
> token replacement and token macro is built around AbstractBuild, which
> pipeline does not use. I am looking into
The biggest hurdle at this point is that email-ext uses token macro for
token replacement and token macro is built around AbstractBuild, which
pipeline does not use. I am looking into adding the capability to token
macro, and thus email-ext. It's something I am actively working on.
On Thu, Apr 21,
Is support planed for a future release?
On Saturday, April 16, 2016 at 2:16:35 PM UTC-4, slide wrote:
>
> No, this is not currently supported. Token macro, which is the basis for
> the SCRIPT token doesn't currently support the type of object that pipeline
> uses.
>
> On Tue, Feb 9, 2016 at 10:3
No, this is not currently supported. Token macro, which is the basis for
the SCRIPT token doesn't currently support the type of object that pipeline
uses.
On Tue, Feb 9, 2016 at 10:32 AM Rinaldo DiGiorgio
wrote:
> I am able to use email-ext with pipeline to send emails. I am trying to
> use jel
I am able to use email-ext with pipeline to send emails. I am trying to
use jelly templates. I do not see an option for the template processor in
the following. I tried adding *SCRIPT* to the body.
emailext attachLog: true, body: ' ${SCRIPT,
template="html/test.groovy"}', subject: 'Test o
12 matches
Mail list logo
