Log parsing rules in Jenkins
The Log Parser Plugin does not support spaces in your pattern.
This can be clearly seen in their source code:
final String ruleParts[] = parsingRule.split("\\s");String regexp = ruleParts[1];They should probably have used .split("\\s", 2).
As an alternative, you can use \s, \b, or an escape sequence - \u0020.
I had tried no spaces in the pattern, but that did not work.Turns out that the Parsing Rules files does not supportempty lines in it. Once I removed the empty lines, I did notget this "Bad parsing rule: , Error:1".
I think since the line is empty - it doesn't echo any rule afterthe first colon. Would have been nice it the line number wasreported where the problem is.