[JIRA] (JENKINS-13892) Static analyis plugins on MBA

naveen karnati created JENKINS-13892:
----------------------------------------

             Summary: Static analyis plugins on MBA
                 Key: JENKINS-13892
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
             Project: Jenkins
          Issue Type: Bug
          Components: plugin
            Reporter: naveen karnati
            Assignee: Ulli Hafner
         Attachments: static_analysis_result_error.JPG

As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong. Let me know if you need further info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

naveen karnati updated JENKINS-13892:
-------------------------------------

        Summary: Static analyis plugins  (was: Static analyis plugins on MBA)
    Description:
As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this

Let me know if you need further info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you.

  was:
As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong. Let me know if you need further info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you.

   

> Static analyis plugins
> ----------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: plugin
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this
> Let me know if you need further info.
> Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163158#comment-163158 ]

Ulli Hafner commented on JENKINS-13892:
---------------------------------------

Can you please show the results of the associated findbugs and compiler warnings? What is shown in the fixed warnigngs tab? Can you please also provide the build summary information for each plug-in?

Seems that the actual warninngs count is based on the result total, while in the detail page duplicates are removed.
               

> Static analyis plugins
> ----------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this
> Let me know if you need further info.
> Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ulli Hafner updated JENKINS-13892:
----------------------------------

    Component/s: analysis-collector
                 analysis-core
                     (was: plugin)
   

> Static analyis plugins
> ----------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this
> Let me know if you need further info.
> Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

naveen karnati updated JENKINS-13892:
-------------------------------------

    Attachment: findbugsresult.JPG
                fixed_warnings_tab.JPG
                compilerwarnings.JPG

Attached is findbugresult, fixed_warnings_tab & compilerwarnings.

Somehow the 12 tests shown as warnings in findbugresult & compilerwarnings, went into fixed in the build analysis result.

Sry.. I didn't get when you are requesting to provide build summary for each plugin. Is it the console output.
               

> Static analyis plugins
> ----------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this
> Let me know if you need further info.
> Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163183#comment-163183 ]

naveen karnati edited comment on JENKINS-13892 at 5/25/12 3:58 AM:
-------------------------------------------------------------------

Attached is findbugresult, fixed_warnings_tab & compilerwarnings.

Somehow the 12 tests shown as warnings in find bug result & compiler warnings, went into fixed in the build analysis result.

The same build passed in the subsequent runs and somehow the build fails intermittently. So I guess it may not be related to duplicates.

Sry.. I didn't get when you are requesting to provide build summary info for each plugin. Is it you want console output

Thank you
               
      was (Author: naveen_karnati):
    Attached is findbugresult, fixed_warnings_tab & compilerwarnings.

Somehow the 12 tests shown as warnings in findbugresult & compilerwarnings, went into fixed in the build analysis result.

Sry.. I didn't get when you are requesting to provide build summary for each plugin. Is it the console output.
                 

> Static analyis plugins
> ----------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this
> Let me know if you need further info.
> Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ulli Hafner updated JENKINS-13892:
----------------------------------

    Summary: Analysis collector marks some warnings as fixed even though they are not  (was: Static analyis plugins)
   

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this
> Let me know if you need further info.
> Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ulli Hafner updated JENKINS-13892:
----------------------------------

    Environment:
Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19
    Description:
As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).



  was:
As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).   Appreciate any insights on this

Let me know if you need further info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you.

   

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-13892 started by Ulli Hafner.

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163347#comment-163347 ]

Ulli Hafner commented on JENKINS-13892:
---------------------------------------

What options did you set in the analysis collector configuration (compute new warnings, use delta for new warnings). What are the warning numbers of the reference build?
               

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163347#comment-163347 ]

Ulli Hafner edited comment on JENKINS-13892 at 5/31/12 12:47 PM:
-----------------------------------------------------------------

What options did you set in the analysis collector configuration (compute new warnings, use delta for new warnings). What are the warning numbers of the reference build (the build that new warnings are computed)?

Does this occur in all of your projects and in all builds? Or is this just a singular problem?
               
      was (Author: drulli):
    What options did you set in the analysis collector configuration (compute new warnings, use delta for new warnings). What are the warning numbers of the reference build?
                 

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

naveen karnati updated JENKINS-13892:
-------------------------------------

    Attachment: publisher_warnings_config_xml_part.txt

This is a singular problem. Occurs in frequently. Attached is the build config.xml during the build fail.
               

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163399#comment-163399 ]

naveen karnati edited comment on JENKINS-13892 at 6/1/12 9:20 AM:
------------------------------------------------------------------

This is a singular problem. Occurs in frequently. Attached is the build config.xml during the build fail.

The warning numbers of reference build(i.e previous build) is as below. This is correct. Due to wrong computation in current build, the next build failed(since the reference changed).

        FindBugs: 13 warnings from one FindBugs analysis.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 85 days!

        Compiler Warnings: 39 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 46 days!

        Static Analysis Warnings: 52 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 16 days!

               
      was (Author: naveen_karnati):
    This is a singular problem. Occurs in frequently. Attached is the build config.xml during the build fail.
                 

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163399#comment-163399 ]

naveen karnati edited comment on JENKINS-13892 at 6/1/12 9:25 AM:
------------------------------------------------------------------

This is a singular problem. Occurs in frequently in only one project. Attached is the build config.xml during the build fail.

The warning numbers of reference build(i.e previous build) is as below. This is correct. Due to wrong computation in current build, the next build failed(since the reference changed).

        FindBugs: 13 warnings from one FindBugs analysis.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 85 days!

        Compiler Warnings: 39 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 46 days!

        Static Analysis Warnings: 52 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 16 days!

               
      was (Author: naveen_karnati):
    This is a singular problem. Occurs in frequently. Attached is the build config.xml during the build fail.

The warning numbers of reference build(i.e previous build) is as below. This is correct. Due to wrong computation in current build, the next build failed(since the reference changed).

        FindBugs: 13 warnings from one FindBugs analysis.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 85 days!

        Compiler Warnings: 39 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 46 days!

        Static Analysis Warnings: 52 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 16 days!

                 

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163399#comment-163399 ]

naveen karnati edited comment on JENKINS-13892 at 6/1/12 9:26 AM:
------------------------------------------------------------------

This is a singular problem. Occurs in frequently in only one project (as of my awareness). Attached is the build config.xml during the build fail.

The warning numbers of reference build(i.e previous build) is as below. This is correct. Due to wrong computation in current build, the next build failed(since the reference changed).

        FindBugs: 13 warnings from one FindBugs analysis.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 85 days!

        Compiler Warnings: 39 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 46 days!

        Static Analysis Warnings: 52 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 16 days!

               
      was (Author: naveen_karnati):
    This is a singular problem. Occurs in frequently in only one project. Attached is the build config.xml during the build fail.

The warning numbers of reference build(i.e previous build) is as below. This is correct. Due to wrong computation in current build, the next build failed(since the reference changed).

        FindBugs: 13 warnings from one FindBugs analysis.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 85 days!

        Compiler Warnings: 39 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 46 days!

        Static Analysis Warnings: 52 warnings.

    Plug-in Result:Success - no threshold has been exceeded
    New highscore: only successful builds for 16 days!

                 

> Analysis collector marks some warnings as fixed even though they are not
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13892
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
>             Project: Jenkins
>          Issue Type: Bug
>          Components: analysis-collector, analysis-core
>         Environment: Jenkins core version: 1.410
> Static Code Analysis Plug-ins -- 1.38
> FindBugs Plugin -- 4.36
> Warnings Plugin-- 3.28
> Analysis Collector Plugin--- 1.19
>            Reporter: naveen karnati
>            Assignee: Ulli Hafner
>         Attachments: compilerwarnings.JPG, findbugsresult.JPG, fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, static_analysis_result_error.JPG
>
>
> As mentioned over comment "https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774&#comment-60918774", the "Static Analysis Result" is showing wrong.
> We (at our company) are using Jenkins core version 1.410 and "Static Code Analysis Plug-ins" plugin installed is v1.38. Somehow the result overview is showing wrong. eg: Total warnings are 52, however in the details it shows as 40. Surprisingly, the difference 12 warnings went into fixed (even without any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Ulli Hafner commented on JENKINS-13892

Analysis collector marks some warnings as fixed even though they are not

Sorry, that I didn't follow up yet... Thanks for the answers. I'm still not finding the error. Can you please also attach the build.xml file that is written to the build folder. I need to see if the numbers are correctly written to file...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

naveen karnati updated JENKINS-13892

Analysis collector marks some warnings as fixed even though they are not

Apologies for delayed response. Attached is the build.xml (I could retrieve the xml file from jobconfighistory plugin we are using). Thanks for your continued support to Jenkins
Change By:	naveen karnati (17/Jul/12 8:51 AM)
Attachment:	build_may21.xml

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Ulli Hafner commented on JENKINS-13892

Analysis collector marks some warnings as fixed even though they are not

Hmm, this file looks like the config.xml Do you have the two build.xml files in the affected two build folders ($JENKINS_HOME/jobs[job name]/[reference build number]/build.xml and $JENKINS_HOME/jobs[job name]/[actual build number]/build.xml)?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

naveen karnati updated JENKINS-13892

Analysis collector marks some warnings as fixed even though they are not

oops.. Attached config.xml rather than build.xml in my earlier post. sry.. Attached is the requested build.xml (both reference & failed). thanks
Change By:	naveen karnati (17/Jul/12 1:34 PM)
Attachment:	failed_build.xml
Attachment:	reference_build.xml

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Ulli Hafner commented on JENKINS-13892

Analysis collector marks some warnings as fixed even though they are not

Thanks for adding the files. I can see from these files that for the analysis collector part some warnings are detected as new, even though they are not. However, I still not see why this is the case. Would it be possible to also attach the 2 analysis.xml files of the build folder? Then I can try to write a unit test that reads these files. Somehow one property of a warning changed (filename, etc.).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira