[
https://issues.jenkins-ci.org/browse/JENKINS-12280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159165#comment-159165
]
torbent commented on JENKINS-12280:
-----------------------------------
Sorry about the delay.
Just checked. Running Jenkins 1.445 and Warnings plugin 3.27 on a test-ish
setup.
Both master and slave are Linux-based.
I get all the warnings I expect, so it seems to be working for me :-)
Now I'll take it into our production environment and check it. It has a Linux
server and both Linux and Windows based slaves. I'll get back tomorrow with the
results of that test.
> Warnings plugin does strange things with a custom parser
> --------------------------------------------------------
>
> Key: JENKINS-12280
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12280
> Project: Jenkins
> Issue Type: Bug
> Components: warnings
> Environment: Linux master, Windows slave.
> Jenkins 1.441, Warnings 3.24.
> Reporter: torbent
> Assignee: Ulli Hafner
>
> I configured a parser in the main Configure section and verified that it
> would match and report a warning. However, it would only report one even if I
> copied extra lines?
> During an actual build (on the slave) it is reported to be run. I see the
> correct parser name (that I gave it), the correct file name of the log file,
> and it claims to have found 4 warnings ("Successfully parsed ... with 4
> warnings").
> The problems are:
> - There should, by my count, be 18 warnings
> - It doesn't actually report warnings from the parser in the "Warnings" result
> There is one other warning parser involved, an MSBuild parser. There are 2
> warnings from that (correct), and I also get 2 warnings from the _not
> configured_ "PC-Lint" parser. The alleged PC-Lint warnings are identical to
> the MSBuild warnings, apart from the type.
> No warnings are reported for my parser.
> It could look like there's some mix-up of parsers? Is this by any chance
> related to JENKINS-11926?
> Further details:
> - Both warnings parsers are run on the same file.
> - The warnings I want to parse do not have file names nor line numbers. I've
> tried putting both "some text" and "" as file name, and 0 or 1 for line
> number. Neither worked any differently.
--
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
