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