This isn't working for me - the script is run but failureCauses.size()
isn't more than 0, even though three causes have been matched in my test
case.
This is Jenkins core 1.546, with BFA 1.5.1 and email-ext 2.37.1 (server is
Ubuntu 12.04, java version 1.7.0_25).
Any ideas what I'm missing?
Mike
jelly script for obtaining information from Build Failure Analyzer plugin
and using it in Email ext plugin
Many thanks to Robert Sandell (one of the developers of BFA) for assisting
me in creating this snippet!
xmlns:d="jelly:define" >
>
> value="${it.getAction('com.sonyericsson.jenkins.
Indeed it is! I hope to have time to get to this at some point.
- David
On Thursday, January 3, 2013 3:37:42 PM UTC+2, slide wrote:
>
> Yes, it does. You could fork the plugin, add the changes in and create a
> pull request. Community Driven Development at its finest.
>
>
> On Thu, Jan 3, 2013 a
Yes, it does. You could fork the plugin, add the changes in and create a
pull request. Community Driven Development at its finest.
On Thu, Jan 3, 2013 at 6:35 AM, David Resnick wrote:
> Right, but the Build Failure Analyzer plugin needs to create a token with
> its output first, doesn't it?
>
>
Right, but the Build Failure Analyzer plugin needs to create a token with
its output first, doesn't it?
- David
On Thursday, January 3, 2013 3:26:43 PM UTC+2, slide wrote:
>
> You can use Token Macro tokens in email-ext content templates.
>
>
> On Thu, Jan 3, 2013 at 6:24 AM, David Resnick
> >
You can use Token Macro tokens in email-ext content templates.
On Thu, Jan 3, 2013 at 6:24 AM, David Resnick wrote:
> Great plugin! It's a huge time saver to have Jenkins figure out what went
> wrong with a build rather than having to view the log and figure it out for
> myself.
>
> Right now I
Great plugin! It's a huge time saver to have Jenkins figure out what went
wrong with a build rather than having to view the log and figure it out for
myself.
Right now I'd say that the biggest improvements that could be made to the
plugin involve making its results more prominent.
It would be
