This plugin generates the trend report for compiler warnings in the console log or in log files.
This plug-in is supported by the Static Analysis Collector plug-in that collects different analysis results and shows the results in aggregated trend graphs. Additionally, health reporting and build stability is also based on the aggregated results.
You need to add the post-build action scan for compiler warnings to actually get warnings. (By default none will be generated.)
Select one or more parsers corresponding to the warnings you want to get. Each parser will generate a specific warning. Parser javac generates Java Warnings. The Maven parser generates Maven Warnings. Etc...
The Warnings plug-in scans the console log or specified log files for warnings of different formats and reports the number of warnings found. This plug-in is part of the suite of static code analysis plug-ins that are documented on a separate WIKI page.
The current release is available in the download section. This plug-in is developed and maintained by Ullrich Hafner. Please use the mailing lists or issue tracker to ask questions, create feature request or bug reports, since I don't read the comment section on this page regularly.
If there is a parser missing, then you can simply extend the available set of parsers using one of the following methods.
Since release 3.8 you can define new parsers dynamically in the system configuration section of Jenkins. Just navigate to http://[jenkins-url]/configure and create a new parser in section Compiler Warnings. The UI should be self explanatory, if there is something missing, please let me know on the mailing lists.
Extending the existing set of supported warning formats is quite easy. If the format of the warnings messages could be parsed by an regular expression, then you only need to provide a new parser class and a corresponding test case:
If your parser is only of interest for your team or company then you can also develop a parser that will be bundled into a separate and private plug-in. The development approach is quite similar:
Skip to end of metadata Go to start of metadata