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

Jacob Larfors commented on JENKINS-13411:
-----------------------------------------

Hello again,

I have contacted Klocwork directly with regards to this to get their input on 
the matter. Their CTO, Gwyn Fisher, has responded with the following:

"
Whilst it may appear at first blush that Klocwork, due to deprecating 
kwinspectreport (note that deprecation in 9.5 means it's gone in 9.6, not 9.5 
itself), is intent on steering people solely through Klocwork Review, this is 
not necessarily the case, although we're always happy to see people use the 
tools we provide (especially as Review is so 'Ooo' and 'Ahhh' these days... 
;p). The old inspect reporting tool had many shortcomings from our perspective, 
not least of which being a login session requirement, something of a security 
hole in any enterprise setting. So in terms of its deprecation and replacement, 
the Web API (JSON over HTTP) is our interface of choice for people creating 
integrations such as with Jenkins or other CI frameworks. If you're concerned 
about the data model change from XML to JSON, and wish to keep your work in the 
XML domain, we have prebuilt examples that show how (in a very small number of 
LOC) to emit the old inspect report schema from the new API in a variety of 
scripting languages.
"

I hope this clarifies any concerns.

Thanks,
Jacob
                
> Klocwork XML output is deprecated
> ---------------------------------
>
>                 Key: JENKINS-13411
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13411
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: klocwork
>            Reporter: Krzysztof Malinowski
>            Assignee: gbois
>
> As http://www.klocwork.com/products/documentation/current/Kwinspectreport 
> states: XML report is deprecated in KW 9.5 and will no longer be available. I 
> recommend that plugin uses some other parser for the issues (csv maybe) or 
> use web api to get the issues.

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


Reply via email to