Massimo, I think that the problem must be somewhere else. Maybe the output file is different. Would it be possible to attach the output as a file? Or conversely, can you check if the attached file issue11926.txt will be parsed by your parser if you copy it to the slave (or master).

Ok, I will try to parse your attached file as soon as possible.
Thanks

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).

Solved.

I did not notice that some colleague of mine slightly changed the format of the output.

Thanks to everybody!
Massimo

Issue reopening was due to an error in usage