CODEWITHSUNDEEP
jenkinsjenkins-pluginsjenkins-pipeline
npatel
npatel

Reputation: 1111

Seeing Bad parsing rule for Jenkins Log parser plugin

I am trying to use Log Parser Plugin with Jenkins. Following is my rule file which I have taken from the sample given on the link.

# match line starting with 'error', case-insensitive
error /(?i)^error/

# list of warnings here...
warning /[Ww]arning/
warning /WARNING/

# create a quick access link to lines in the report containing 'INFO'
info /INFO/

# each line containing 'BUILD' represents the start of a section for grouping errors and warnings found after the line.
# also creates a quick access link.
start /BUILD/

I still see following at the end of the Parsed Console Output page:

NOTE: Some bad parsing rules have been found:
Bad parsing rule: , Error:1
Bad parsing rule: , Error:1
Bad parsing rule: , Error:1

I did come across this, but dint help as I am not using space anywhere.

Can someone help me resolving this issue?

Upvotes: 2

Views: 1074

Answers (2)

Aviator
Aviator

Reputation: 107

I had tried no spaces in the pattern, but that did not work. Turns out that the Parsing Rules files does not support empty lines in it. Once I removed the empty lines, I did not get this "Bad parsing rule: , Error:1".

I think since the line is empty - it doesn't echo any rule after the first colon. Would have been nice it the line number was reported where the problem is.

I posted the same to this thread too - Log parsing rules in Jenkins

Hopefully, it helps out other folks who may be wondering what is causing this.

Upvotes: 0

Joe
Joe

Reputation: 512

It appears you have extra white-space somewhere in the file that the plugin is interpreting as you attempting to define a rule. Maybe try running it with the empty lines removed. That plugin has given me quite a bit of trouble as well, it's not very well documented (as is the case with many Jenkins plugins).

Upvotes: 4

Related Questions