Jenkins › Jenkins issues

[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

Classic

List

Threaded

3 messages Options

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

Greg Moncreaff created JENKINS-12860:
----------------------------------------

Summary: klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets
Key: JENKINS-12860
URL: https://issues.jenkins-ci.org/browse/JENKINS-12860
Project: Jenkins
Issue Type: Improvement
Components: analysis-core, klocwork
Environment: rhel 5.5
Reporter: Greg Moncreaff
Assignee: Ulli Hafner

klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

--
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

Remove Ads

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

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

Ulli Hafner reassigned JENKINS-12860:
-------------------------------------

Assignee: gbois (was: Ulli Hafner)

How is the current implememtation working? Is this a text or xml file that is parsed and then gets visualized?

A simple solution would be to just implement a parser for the warnings plugin. Of course using analysis-core would work, too.

What do you think?

> klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets
> ------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-12860
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12860
> Project: Jenkins
> Issue Type: Improvement
> Components: analysis-core, klocwork
> Environment: rhel 5.5
> Reporter: Greg Moncreaff
> Assignee: gbois
>
> klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

--
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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

In reply to this post by JIRA noreply@jenkins-ci.org

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

Greg Moncreaff commented on JENKINS-12860:
------------------------------------------

In order of preference:

1. make the static analysis collector, et al have a tool agnostic generic mechanism for reporting issues with tool provided types and categories.
(along the lines of xUnit where all test results are normalized to a common form?)
2a. have an xslt that transforms klocwork xml format to the already handled findbugs format or
2b. (this request) add klocwork as another tool using SA/AC
3. have warnings plugin be able to publish a portlet like SA's warnings (trend by type and per project) where the types of each built in or ad hoc parser gets its on line/column (another request made a few weeks back).
4. (what I'm currently doing) is a bunch of adhoc console parsers based on the text report from klocwork.

What I have works, but I thing any of 1 2 or 3 would obviously be a better foundation not just for klocwork, but for any other tool producing analysis results.