This brute force sed script seems to help

${KWS}/kwinspectreport --build build_${BUILD} --url ${KWDB}/${PROJECT} -xml ${FILE}.raw

1. try and filter out some of the 9.5.x new tags that make the Jenkins publisher unhappy
   cat ${FILE}.raw | egrep -v "(<trace|<taxonom|<.taxonomies|<.trace|<owner)" > ${FILE}

Info for maintainer: current output is:

<?xml version="1.0" encoding="UTF-8"?>
<errorList xmlns="http://www.klocwork.com/inForce/report/1.0" version="9.5.2">
<problem>
 <problemID>1</problemID>
 <file>/path/to/hello.c</file>
 <method>main</method>
 <line>8</line>
 <column>5</column>
 <code>UNINIT.STACK.MUST</code>
 <message>&apos;p&apos; is used uninitialized in this function.</message>
 <anchor>112</anchor>
 <prefix>ain(intargc,char*argv[]){char*p;</prefix>
 <postfix>return0;}</postfix>
 <trace>
  <traceBlock file="/path/to/hello.c" method="main" id="0">
   <traceLine line="7" text="&apos;p&apos; is declared" type="E"/>
   <traceLine line="8" text="&apos;p&apos; is used, but is uninitialized." type="E"/>
  </traceBlock>
 </trace>
 <citingStatus>Analyze</citingStatus>
 <state>New</state>
 <owner>unowned</owner>
 <severity>Critical</severity>
 <severitylevel>1</severitylevel>
 <displayAs>Error</displayAs>
 <taxonomies>
  <taxonomy name="C and C++" metaInf=""/>
 </taxonomies>
 <dateOriginated>1331140856962</dateOriginated>
 <url>http://klocworkserver:8074/review/insight-review.html#goto:project=test,pid=1</url>
</problem>
</errorList>

Also, is there any way the KW issues data grid can include the URL to the issue on the KW project server as some form of shortcut, so they full highlighting and trace can be accessed there in?

Would you like a release?

I think yes?

Well, I'd like a release for sure
I'm using plugin 1.10 with KW 9.5.3 and the following stack trace appears (see below). Is it perhaps this issue?

ERROR: Publisher com.thalesgroup.hudson.plugins.klocwork.KloPublisher aborted due to exception
java.lang.NullPointerException
at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.perform(KloPublisher.java:101)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
at hudson.model.Run.execute(Run.java:1527)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
[xUnit] [INFO] - Starting to record.

Hello,
It doesn't seem to work fine with 1.12
I'm using KW 9.5.3, and that's what I got in build log:

==============================
Starting the klocwork analysis.
Version 9.6 or later of Klocwork detected. Only Klocwork review is available. Parse_errors.log and build.log can be accessed on the review
ERROR: Publisher com.thalesgroup.hudson.plugins.klocwork.KloPublisher aborted due to exception
java.lang.NullPointerException
at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.perform(KloPublisher.java:186)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
at hudson.model.Run.execute(Run.java:1527)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
[xUnit] [INFO] - Starting to record.

The issue persists in another code part.

The issue should be fix in 1.13.
I'm afraid the initial code misses many checks.
Please let me know if you have further problems.

I'll give it a try. Thank you!
BTW, could you please write what logger should I subscribe to to gather some more kw plugin debug information in future?

I'm afraid I don't understand your last question about logger.
Do you ask me which kind of tool to use when you'll have new issues?
Thanks

OK, so let me rephrase it; perhaps I wasn't too clear, indeed.
Is there a way that I could gather some more detailed logs from the Klocwork plugin?
Waldek