@Massimo Rossello: can you please attach the new console output?

In my environment with the custom parser the problem is solved with 3.27!

@Ulli
I tried again both a Windows master + Linux slave with Jenkins 1.450, and a Linux + Linux with Jenkins 1.451.
I still have the same console output:

[WARNINGS] Parsing warnings in files 'flexelint.txt' with parser MyLint
[WARNINGS] Parsing 1 files in /opt/server/workspace/prova
[WARNINGS] Successfully parsed file /opt/server/workspace/prova/flexelint.txt of module  with 0 warnings.

Sorry, on the Linux+Linux configuration it was a mistake of mine. As soon as I'll have access to the system, I check again the Windows+Linux configuration.

Thanks

Hi,
I confirm that the Windows master (Jenkins 1.450) + Linux slave configuration DOES NOT work with 3.27. I see no progress at all.

This problem is coupled (as before) with a strange behavior on the master configuration page. Whenever the example parsed text is over about 250 characters, a match is no more found (even if more text is appended after a previously matched text).

Here is my current output:

[WARNINGS] Parsing warnings in files 'reports/flexelint.txt' with parser AzcomLint
[WARNINGS] Parsing 1 files in /opt/server/jenkins/workspace/customer1_continuous_trunk
[WARNINGS] Successfully parsed file /opt/server/jenkins/workspace/customer1_continuous_trunk/reports/flexelint.txt of module  with 0 warnings.
[WARNINGS] Computing warning deltas based on reference build #600

Regards

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