Static analysis plugins fails to see the differences between builds

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Static analysis plugins fails to see the differences between builds

Jeroen Visser
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?

Thanks.
Jeroen


Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Ulli Hafner
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli
Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Jeroen Visser
Im using a Maven job (multimodule).
I have used this plugin before on Hudson also with Maven job type and it worked perfectly then.

I will file an issue later today.

Thanks,
Jeroen 

On Tue, Jun 7, 2011 at 4:14 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli

Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Ulli Hafner
I think I found the bug, I'm having the snapshot release running at http://faktorlogik.de:8081/view/Jenkins/

I'll prepare a new release right now...

Ulli

On 06/08/2011 11:14 AM, Jeroen Visser wrote:
Im using a Maven job (multimodule).
I have used this plugin before on Hudson also with Maven job type and it worked perfectly then.

I will file an issue later today.

Thanks,
Jeroen 

On Tue, Jun 7, 2011 at 4:14 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli


Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Jeroen Visser
Ok nice, looking forward to it.
Thanks for the quick response.

Jeroen

On Wed, Jun 8, 2011 at 10:46 PM, Ulli Hafner <[hidden email]> wrote:
I think I found the bug, I'm having the snapshot release running at http://faktorlogik.de:8081/view/Jenkins/

I'll prepare a new release right now...

Ulli


On 06/08/2011 11:14 AM, Jeroen Visser wrote:
Im using a Maven job (multimodule).
I have used this plugin before on Hudson also with Maven job type and it worked perfectly then.

I will file an issue later today.

Thanks,
Jeroen 

On Tue, Jun 7, 2011 at 4:14 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli



Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

nileshagrawal02
This post has NOT been accepted by the mailing list yet.
Hello, Similar issue exists for PMD plugin as well I guess. I wasn't seeing the trend graphs for PMD, Check Style and Find Bugs but after todays' latest plugin for CheckStyle and FindBugs, issues with respective reports were fixed. Issue still exists with PMD plugin I guess.
Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Jeroen Visser
In reply to this post by Jeroen Visser
Hi,

Plugin seems to detect the differences correctly now (on the build page of the job).
The only problem I still have is that specifically for PMD I dont get a trend chart on the job main page en no result in the "Warnings per project" dashboard widget.
I do get a chart for duplicate code and open tasks.

Jeroen

On Thu, Jun 9, 2011 at 10:17 AM, Jeroen Visser <[hidden email]> wrote:
Ok nice, looking forward to it.
Thanks for the quick response.

Jeroen

On Wed, Jun 8, 2011 at 10:46 PM, Ulli Hafner <[hidden email]> wrote:
I think I found the bug, I'm having the snapshot release running at http://faktorlogik.de:8081/view/Jenkins/

I'll prepare a new release right now...

Ulli


On 06/08/2011 11:14 AM, Jeroen Visser wrote:
Im using a Maven job (multimodule).
I have used this plugin before on Hudson also with Maven job type and it worked perfectly then.

I will file an issue later today.

Thanks,
Jeroen 

On Tue, Jun 7, 2011 at 4:14 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli




Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Ulli Hafner
On 06/15/2011 03:36 PM, Jeroen Visser wrote:
Hi,

Plugin seems to detect the differences correctly now (on the build page of the job).
The only problem I still have is that specifically for PMD I dont get a trend chart on the job main page en no result in the "Warnings per project" dashboard widget.
I do get a chart for duplicate code and open tasks.

I think I just forgot to release PMD, too. Can you please retry to see if version 3.17 is available now?

Ulli


Jeroen

On Thu, Jun 9, 2011 at 10:17 AM, Jeroen Visser <[hidden email]> wrote:
Ok nice, looking forward to it.
Thanks for the quick response.

Jeroen

On Wed, Jun 8, 2011 at 10:46 PM, Ulli Hafner <[hidden email]> wrote:
I think I found the bug, I'm having the snapshot release running at http://faktorlogik.de:8081/view/Jenkins/

I'll prepare a new release right now...

Ulli


On 06/08/2011 11:14 AM, Jeroen Visser wrote:
Im using a Maven job (multimodule).
I have used this plugin before on Hudson also with Maven job type and it worked perfectly then.

I will file an issue later today.

Thanks,
Jeroen 

On Tue, Jun 7, 2011 at 4:14 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli





Reply | Threaded
Open this post in threaded view
|

Re: Static analysis plugins fails to see the differences between builds

Jeroen Visser
Yes I updated to 3.17 PMD stats and chart work now.

Thanks,
Jeroen

On Wed, Jun 15, 2011 at 3:42 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/15/2011 03:36 PM, Jeroen Visser wrote:
Hi,

Plugin seems to detect the differences correctly now (on the build page of the job).
The only problem I still have is that specifically for PMD I dont get a trend chart on the job main page en no result in the "Warnings per project" dashboard widget.
I do get a chart for duplicate code and open tasks.

I think I just forgot to release PMD, too. Can you please retry to see if version 3.17 is available now?

Ulli



Jeroen

On Thu, Jun 9, 2011 at 10:17 AM, Jeroen Visser <[hidden email]> wrote:
Ok nice, looking forward to it.
Thanks for the quick response.

Jeroen

On Wed, Jun 8, 2011 at 10:46 PM, Ulli Hafner <[hidden email]> wrote:
I think I found the bug, I'm having the snapshot release running at http://faktorlogik.de:8081/view/Jenkins/

I'll prepare a new release right now...

Ulli


On 06/08/2011 11:14 AM, Jeroen Visser wrote:
Im using a Maven job (multimodule).
I have used this plugin before on Hudson also with Maven job type and it worked perfectly then.

I will file an issue later today.

Thanks,
Jeroen 

On Tue, Jun 7, 2011 at 4:14 PM, Ullrich Hafner <[hidden email]> wrote:
On 06/07/2011 03:43 PM, Jeroen Visser wrote:
Hello,

It seems Jenkins PMD/DRY and TASK scanner plugins fail to see the relation between builds (compiler warnings plugins does work as expected).

I dont get any results on the main page of the specific job (and thus no trend charts).
On the build pages of the job I get the results but only the absolute numbers and not the difference with the last build.

On the dashboard view in the Jenkins front page I have the "Warnings per project" widget which just shows "-" for each type of warning (except compiler warnings which works as expected).

The plugins seem to scan the results succesfully, yet fail to see the difference with the last build.

Log snippet:
[PMD] Aggregating results of ASText
[PMD] Using set difference to compute new warnings
[PMD] Not changing build status, since no threshold has been exceeded
[DRY] Aggregating results of Commons
[DRY] Using set difference to compute new warnings
[DRY] Not changing build status, since no threshold has been exceeded

Any ideas as to what might be causing this?


This seems to be a bug. Can you please file an issue?

Are you using the maven job type? Or freestyle?

Thanks, Ulli