[
https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158881#comment-158881
]
Hendrik Fuß commented on JENKINS-11926:
---------------------------------------
In fact I have a problem with Warnings in a setup with a Linux master and a
Windows 7 slave, and 3.27 didn't solve it. However, I'm not using a custom
parser.
In my case, Warnings reports the number if warnings found and then throws an
IOException (or similar). Will post the stack trace when I'm back at work next
week.
> Warnings plugin does not work on a slave
> ----------------------------------------
>
> Key: JENKINS-11926
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11926
> Project: Jenkins
> Issue Type: Bug
> Components: warnings
> Affects Versions: current
> Environment: Tried both with:
> - a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24
> - a linux box (different from the above) acting both as master and slave,
> Jenkins 1.440, Warnings 3.24
> Reporter: Massimo Rossello
> Assignee: Ulli Hafner
> Labels: plugin, slave, warnings
>
> I create my own parser. If I use the Warning parsing on the master it works
> as expected. If I make the parsing on the slave it always reports 0 warnings
--
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
