Hi, I'll recommend that you switch to Groovy templates, they are far easier to work with than Jelly templates. With that being said, you need to look at the API's available for the Violations plugin, then you would access the Violations action for the specific build using AbstractBuild.getActions, find the action you need so that you have access to the API and then use the API of whatever the Violations plugin provides.
Slide On Tue, Jul 16, 2013 at 8:22 PM, Daniel Becroft <djcbecr...@gmail.com>wrote: > Hi, > > Does anyone have an example of accessing the Violations information > (StyleCop, FxCop, etc) in a jelly email template? Or some documentation on > how it would be accessible? > > We are looking to start failing the build on violation counts, and it > would be good if we can include information regarding what triggered the > failure in the email. > > Regards, > --- > Daniel Becroft > > -- > 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. > > > -- Website: http://earl-of-code.com -- 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.