static analysis - detecting new warnings

[Two Wheels]

Hi,
I'm using various static analysis tools/plugins such as FindBugs,
Flawfinder, PMD, Cppcheck.
Does anyone know if there is a way of detecting new warnings so that I
can do such things as send out an email.
Also, can the detection identify the actual code line where the new
warning was introduced.
Thanks !

[Mark Waite]

The findbugs plugin provides links to new warnings for each build that is run.  It also provides links to fixed warnings so you know what was improved in that build.  

The findbugs plugin links and pages show the findbugs warning summary, its details, and the file and line number in the user interface.  I find it very easy and very reliable to go from the findbugs plugin line number output to the source code.

I know there is at least one team that I support which has their Jenkins job configured to send e-mail when a new warning is introduced, so I am reasonably confident that can be done as well.  I believe they are using one of the mail notification plugins to perform that task.

Mark Waite

---

From: Nig <[hidden email]>
To: Jenkins Users <[hidden email]>
Sent: Friday, December 30, 2011 4:32 AM
Subject: static analysis - detecting new warnings

Hi,
I'm using various static analysis tools/plugins such as FindBugs,
Flawfinder, PMD, Cppcheck.
Does anyone know if there is a way of detecting new warnings so that I
can do such things as send out an email.
Also, can the detection identify the actual code line where the new
warning was introduced.
Thanks !

[Eyal Edri]

----- Original Message -----

> From: "Mark Waite" <[hidden email]>
> To: [hidden email]
> Sent: Friday, December 30, 2011 4:00:35 PM
> Subject: Re: static analysis - detecting new warnings
>
> The findbugs plugin provides links to new warnings for each build
> that is run.  It also provides links to fixed warnings so you know
> what was improved in that build.
>
> The findbugs plugin links and pages show the findbugs warning
> summary, its details, and the file and line number in the user
> interface.  I find it very easy and very reliable to go from the
> findbugs plugin line number output to the source code.
>
> I know there is at least one team that I support which has their
> Jenkins job configured to send e-mail when a new warning is
> introduced, so I am reasonably confident that can be done as well.
>  I believe they are using one of the mail notification plugins to
> perform that task.

we do that in RHEVM/oVirt products.
we want to know on any new HIGH Priority bugs introduced in the build, so i set the limit of high to '0' on the 'advanced' tab
for the findbugs option in the job configuration.
and i tick also the 'Use rank as priority' option.

>
>
> Mark Waite
>
>
>
> >________________________________
> > From: Nig <[hidden email]>
> >To: Jenkins Users <[hidden email]>
> >Sent: Friday, December 30, 2011 4:32 AM
> >Subject: static analysis - detecting new warnings
> >
> >Hi,
> >I'm using various static analysis tools/plugins such as FindBugs,
> >Flawfinder, PMD, Cppcheck.
> >Does anyone know if there is a way of detecting new warnings so that
> >I
> >can do such things as send out an email.
> >Also, can the detection identify the actual code line where the new
> >warning was introduced.
> >Thanks !
> >
> >
> >

[Ulli Hafner]

As already mentioned by Mark, this is possible for findbugs and PMD (and
for checkstyle, and cpd as well).
I think it also works for Cppcheck.
See
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins

Ulli


On 12/31/2011 10:49 AM, Eyal Edri wrote:

>
> ----- Original Message -----
>> From: "Mark Waite"<[hidden email]>
>> To: [hidden email]
>> Sent: Friday, December 30, 2011 4:00:35 PM
>> Subject: Re: static analysis - detecting new warnings
>>
>> The findbugs plugin provides links to new warnings for each build
>> that is run.  It also provides links to fixed warnings so you know
>> what was improved in that build.
>>
>> The findbugs plugin links and pages show the findbugs warning
>> summary, its details, and the file and line number in the user
>> interface.  I find it very easy and very reliable to go from the
>> findbugs plugin line number output to the source code.
>>
>> I know there is at least one team that I support which has their
>> Jenkins job configured to send e-mail when a new warning is
>> introduced, so I am reasonably confident that can be done as well.
>>   I believe they are using one of the mail notification plugins to
>> perform that task.
> we do that in RHEVM/oVirt products.
> we want to know on any new HIGH Priority bugs introduced in the build, so i set the limit of high to '0' on the 'advanced' tab
> for the findbugs option in the job configuration.
> and i tick also the 'Use rank as priority' option.
>
>
>>
>> Mark Waite
>>
>>
>>
>>> ________________________________
>>> From: Nig<[hidden email]>
>>> To: Jenkins Users<[hidden email]>
>>> Sent: Friday, December 30, 2011 4:32 AM
>>> Subject: static analysis - detecting new warnings
>>>
>>> Hi,
>>> I'm using various static analysis tools/plugins such as FindBugs,
>>> Flawfinder, PMD, Cppcheck.
>>> Does anyone know if there is a way of detecting new warnings so that
>>> I
>>> can do such things as send out an email.
>>> Also, can the detection identify the actual code line where the new
>>> warning was introduced.
>>> Thanks !
>>>
>>>
>>>

[Ulli Hafner]

No, each plug-in has its own section. E.g., click on the 'Advanced' button in the dry plug-in section and enter a value of 0 in a new warnings entry field.

Ulli

On 01/04/2012 04:28 PM, Nigel Robbins wrote:

Hi Ulli,

Sorry to bother you again but can I please have some more help.
In the URL you mentioned, is it the Build Tokens section ?
In my test job I scan for duplicate code and open tasks and would like to send an email if CPD_NEW or TASKS_NEW is greater than 0.
Not sure where to put the code for this ?

Many thanks,
Nigel

> Date: Tue, 3 Jan 2012 14:58:17 +0100
> From: [hidden email]
> To: [hidden email]
> CC: [hidden email]
> Subject: Re: static analysis - detecting new warnings
>
> As already mentioned by Mark, this is possible for findbugs and PMD (and
> for checkstyle, and cpd as well).
> I think it also works for Cppcheck.
> See
> https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins
>
> Ulli
>
>
> On 12/31/2011 10:49 AM, Eyal Edri wrote:
> >
> > ----- Original Message -----
> >> From: "Mark Waite"[hidden email]
> >> To: [hidden email]
> >> Sent: Friday, December 30, 2011 4:00:35 PM
> >> Subject: Re: static analysis - detecting new warnings
> >>
> >> The findbugs plugin provides links to new warnings for each build
> >> that is run. It also provides links to fixed warnings so you know
> >> what was improved in that build.
> >>
> >> The findbugs plugin links and pages show the findbugs warning
> >> summary, its details, and the file and line number in the user
> >> interface. I find it very easy and very reliable to go from the
> >> findbugs plugin line number output to the source code.
> >>
> >> I know there is at least one team that I support which has their
> >> Jenkins job configured to send e-mail when a new warning is
> >> introduced, so I am reasonably confident that can be done as well.
> >> I believe they are using one of the mail notification plugins to
> >> perform that task.
> > we do that in RHEVM/oVirt products.
> > we want to know on any new HIGH Priority bugs introduced in the build, so i set the limit of high to '0' on the 'advanced' tab
> > for the findbugs option in the job configuration.
> > and i tick also the 'Use rank as priority' option.
> >
> >
> >>
> >> Mark Waite
> >>
> >>
> >>
> >>> ________________________________
> >>> From: Nig[hidden email]
> >>> To: Jenkins Users[hidden email]
> >>> Sent: Friday, December 30, 2011 4:32 AM
> >>> Subject: static analysis - detecting new warnings
> >>>
> >>> Hi,
> >>> I'm using various static analysis tools/plugins such as FindBugs,
> >>> Flawfinder, PMD, Cppcheck.
> >>> Does anyone know if there is a way of detecting new warnings so that
> >>> I
> >>> can do such things as send out an email.
> >>> Also, can the detection identify the actual code line where the new
> >>> warning was introduced.
> >>> Thanks !
> >>>
> >>>
> >>>
>