[
https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159182#comment-159182
]
torbent commented on JENKINS-11926:
-----------------------------------
Wild guesses; maybe helpful, maybe confusing:
* Permission problem? Is the log file readable on the slave by the user that
runs the Jenkins service?
* In our setup, the workspaces are on network drives and reachable from both
master and slave (although not at identical paths). Could it be that both
server and slave need access to the workspace for dynamic warnings parsing to
work?
* Or perhaps the expression just doesn't match? For example I'd guess that $5
is wrong (should probably be (.*)). Does the dynamic parser expect to be able
to match a whole line?
* Did you happen to forget restarting Jenkins after installing Warnings 3.27?
Hope this helps. My very similar JENKINS-12280 issue seems to be solved by
version 3.27 (a little extra test is still pending).
> 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
> Attachments: issue11926.txt
>
>
> 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
