Maybe it would be easier to improve the regexp in each parser. Can you please show an example log message that is picked by two parsers?

(BTW: you can redirect the output to a file to get the desired result)

usecase/example log:
i'll need a week or two to reproduce this.

redirection:
(on windows) i do not know a way to redirect the output of build steps to a file and to the jenkins-console or can this be done by means of on-board jenkins functionality?
Having no console output on jenkins is somehow no option since you loose the little progress indicator you have for a 1h build job.

I'll add examples for "false positives" as i encounter them:

This is a line that i see when i run doxygen generation:
Problems running dot: exit code=-1, command='dot', arguments='"D:/jenkins/jobs/myjob/WORKSP~1/BUILDT~1/somefolder/doxydoc/html/d6/d52/structt_something_collgraph.dot" -Tpng -o "D:/jenkins/jobs/myjob/WORKSP~1/BUILDT~1/somefolder/doxydoc/html/d6/d52/structt_somethingcoll_graph.png"'

This line is then matched by the "Texas Instruments" parser.

Code changed in jenkins
User: Ulli Hafner
Path:
src/test/resources/hudson/plugins/warnings/parser/ticcs.txt
http://jenkins-ci.org/commit/warnings-plugin/37dd59559c3317e3f83327f7d066a8952801e552
Log:
Tried to reproduce JENKINS-28174.

Can you please check if the added line matches the line you identified? If not, please wrap the affected line in noformat blocks so Jira will not reformat them.

The unit test does not report this line as a warning...

I'm very sorry, i didn't copy the whole line! besides the "error:" at the beginning, the quotationmarks seem to be correct!

Here's the whole line:
error: Problems running dot: exit code=-1, command='dot', arguments='"D:/testproject/doxydoc/html/inherit_graph_63.dot" -Tpng -o "D:/testproject/doxydoc/html/inherit_graph_63.png"'

I tried this with some online regex tester and there's a match:
http://fiddle.re/86wnj6 (click on the green "java" button)

I see. These warnings are nearly identical. The only difference is a missing : in the Texas Instruments warning. I don't think that it is a good idea to check for the absence of the :, so an update of the regexp is nearly impossible...

As a workaround I suggest that you pipe the output of your build steps to a file and then use a different parser for each file.

Code changed in jenkins
User: Ulli Hafner
Path:
warnings
http://jenkins-ci.org/commit/analysis-suite-plugin/e15113485ce95b7dedcbe0becc1ccb176a88e76f
Log:
Tried to reproduce JENKINS-28174.

I think it would be much simpler to pipe the result to a file and use the files parser.