Re: email-ext tokens for Build Failure Analyzer
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
On Tue, Dec 17, 2013 at 8:40 AM, Adam Guja adam.g...@gmail.com wrote:
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!
j:jelly xmlns:j=jelly:core xmlns:st=jelly:stapler
xmlns:d=jelly:define
BODY
j:set var=failureCauses
value=${it.getAction('com.sonyericsson.jenkins.plugins.bfa.model.FailureCauseBuildAction').getFoundFailureCauses()}/
j:if test=${failureCauses.size() gt 0}
j:forEach var=cause items=${failureCauses}
${cause.name}
br/
${cause.description}
br/
/j:forEach
/j:if
/BODY
/j:jelly
W dniu czwartek, 3 stycznia 2013 14:24:54 UTC+1 użytkownik David Resnick
napisał:
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 great if there was a failure reason email-ext token I could
add to failure emails Jenkins sends out. I've seen that some plugins
produce tokens for use by other plugins, apparently with the help of the
Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/
display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-
tokens ).
Also, the identified problems that appear in a build summary page is
last on the page, seemingly following everything else. As far as I'm
concerned, because of its importance it should be the very first item on
the summary page.
The lightbulb is a great way of seeing what happened with various builds
without further clicking. Depending on how long descriptions are, it might
be good to include additional information in the lightbulb tooltip such as
the description or category.
In any case, thanks for a very helpful plugin.
- David
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: email-ext tokens for Build Failure Analyzer
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!
j:jelly xmlns:j=jelly:core xmlns:st=jelly:stapler
xmlns:d=jelly:define
BODY
j:set var=failureCauses
value=${it.getAction('com.sonyericsson.jenkins.plugins.bfa.model.FailureCauseBuildAction').getFoundFailureCauses()}/
j:if test=${failureCauses.size() gt 0}
j:forEach var=cause items=${failureCauses}
${cause.name}
br/
${cause.description}
br/
/j:forEach
/j:if
/BODY
/j:jelly
W dniu czwartek, 3 stycznia 2013 14:24:54 UTC+1 użytkownik David Resnick
napisał:
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 great if there was a failure reason email-ext token I could
add to failure emails Jenkins sends out. I've seen that some plugins
produce tokens for use by other plugins, apparently with the help of the
Token Macro Plugin (e.g.
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens).
Also, the identified problems that appear in a build summary page is
last on the page, seemingly following everything else. As far as I'm
concerned, because of its importance it should be the very first item on
the summary page.
The lightbulb is a great way of seeing what happened with various builds
without further clicking. Depending on how long descriptions are, it might
be good to include additional information in the lightbulb tooltip such as
the description or category.
In any case, thanks for a very helpful plugin.
- David
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: email-ext tokens for Build Failure Analyzer
You can use Token Macro tokens in email-ext content templates. On Thu, Jan 3, 2013 at 6:24 AM, David Resnick abune...@gmail.com 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'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.com
Re: email-ext tokens for Build Failure Analyzer
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 abun...@gmail.comjavascript: 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'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.com
Re: email-ext tokens for Build Failure Analyzer
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 abune...@gmail.com wrote: 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 abun...@gmail.com 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'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/** display/JENKINS/Static+Code+**Analysis+Plug-ins#** StaticCodeAnalysisPlug-ins-**tokenshttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.**com http://earl-of-code.com -- Website: http://earl-of-code.com
Re: email-ext tokens for Build Failure Analyzer
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 at 6:35 AM, David Resnick abun...@gmail.comjavascript: wrote: 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 abun...@gmail.com 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'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/** display/JENKINS/Static+Code+**Analysis+Plug-ins#** StaticCodeAnalysisPlug-ins-**tokenshttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.**com http://earl-of-code.com -- Website: http://earl-of-code.com
