I'd like to! Unfortunately I'm a user, not a developer (at least not
Jenkins/Clover/Robot one).
Are you talking about cloning the whole plug-in or just the jelly
template? I hoped the static-analysis.jelly could be just extended to
incorporate the data available from the corresponding Jenkins plug-ins.
Do you have some insights about whether all plug-ins should adhere to
the same schema in terms of exposing the collected data? Where could I
look into to find out the proper Objects and their methods to include
them into the jelly template?

Michael

-----Original Message-----
From: Ullrich Hafner [mailto:ullrich.haf...@gmail.com] 
Sent: Thursday, May 31, 2012 3:28 PM
To: jenkinsci-users@googlegroups.com
Cc: Michael Polinovskiy
Subject: Re: Email with pmd | checkstyle

Well, I don't use these tools. But it is quite easy to clone the
email-ext plug-in and create a pull request:-) Are you volunteering?

Ulli


On 05/31/2012 12:39 PM, Michael Polinovskiy wrote:
> Hi Ulli,
>
> great job, thanks!
> Wouldn't it be possible somehow to add a template for Clover and Robot

> Framework?
>
> Regards,
> Michael
>
> -----Original Message-----
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ullrich Hafner
> Sent: Tuesday, May 22, 2012 12:28 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Email with pmd | checkstyle
>
> On 05/22/2012 11:49 AM, arjun tr wrote:
>> I was trying to include short summary of cobertura, pmd, checkstyle, 
>> findbugs reports in emails.
>> I was able to get configurations for cobertura but not for others 
>> with jelly.
>> Is there any place which details on the other plugin configurations 
>> and class, method definitions in either jelly or groovy??
> I added a new template in the latest release of the email-ext plug-in:
> https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/res
> ou rces/hudson/plugins/emailext/templates/static-analysis.jelly
>
> It simply shows the total number of warnings for each of the analysis 
> tools.
>
> Ulli
>
>

Reply via email to