Parse the console output and highlight error/warning/info lines.
The log-parser plugin parses the console log generated by the Jenkins build. Parsing the console log allows for the following features:
This shows a summary of errors and warnings on the build page
This is an example of a parsed log of a build.
The left side of the report can be expanded to browse the errors/warning/info lines. These lines are links to the full log on the right, where they can be easily located. Clicking on a certain error will bring you right to it on the full log which appears on the right side of the screen. The log is also divided into logical sections (as defined in the parsing rules configuration described below). In the summary section on the left you can see the errors/warnings as they appear in the log sections. This can help understand in what part of the build there is an error/warning. Both summary and log sections are scrollable and expandable.
Several parsing options are configured at the global level.
Appears in the global Jenkins configs as section "Console Output Parsing"
For each parsing rules option, specify :
Each line in the file specifies a level (ok/error/warn/info/start) and a regular expression delimited by slashes ("/") to look for in order to mark the line as matching that level.
For example, the following line in the parsing rules file means that a line including the word "ERROR" will be marked as an error line:
Example parsing rules file:
Skip to end of metadata Go to start of metadata