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.
It is accessible from the "Parsed Console Output" link on the left side of the build page :
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"
Configure pairs of logical names (project, description, etc.) and parsing rule files.
Later on, when a job is configured for log parsing, you will be able to choose one of these configurations to implement as the parsing rules for that job. (See "Job Configuration")
For each parsing rules option, specify :
Parsing rule name - logical name which will be displayed in the job level configuration as an option
Parsing Rules File - A file with the parsing rules implemented in this option. (See "Parsing rules files" to learn more about the syntax of these files.)
Each line in the file specifies a level (ok/error/warn/info/start) and a regular expression (based on java.util.regex.Pattern) 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:
error /(?i)^error /
ok /^javadoc:/ error /Error/
javadoc: Error : could not find something
^javadoc:pattern is matched first.
Example parsing rules file:
ok /not really/ # 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/
This section collects some useful additional parse-statements contributed by users of the Log Parser Plugin
error /Execution data for class .* does not match./