Plugin Information
This plugin generates the trend report for compiler warnings in the console log or in log files.
 | Installation Requirements
This plug-in requires the utility plug-in "analysis-core" (called "Static Analysis Utilities" in the update manager). Please ensure that the latest version of this plug-in is also installed. |
Description
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.
The Warnings plug-in scans the console log or specified log files for compiler warnings 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.
- Support for javac (ant, maven, command line), Eclipse Java Compiler, JavaDoc Compiler, Hudson HPI, MSBuild, GCC, GNU Linker, SUN Studio C++, Gnat (Ada), Erlang, PC-Lint compiler warnings (configuration of PcLint), Eclipse Buckminster and Oracle Invalids
- Build summary showing the new and fixed warnings of a build
- Several trend reports showing the number of warnings per build
- Overview of the found warnings per module, package, category, or type
- Parsing of Maven pom.xml or Ant build.xml configuration files to obtain the module or project name
- Parsing of Java or C# files to obtain the package or name space name
- Detail reports of the found warnings optionally filtered by severity (or new and fixed)
- Colored HTML display of the corresponding source file and warning lines:
- Direct link to the warning line
- Highlighting of single lines as well as line ranges
- Highlighting of multiple line ranges per warning (different color for primary range)
- Tool tip describing the warning message
- Failure threshold to mark a build as unstable
- Configurable project health support
- Works with the freestyle and native m2 build option of Hudson (activated on goal compile)
- Remote API to export the build quality and found warnings
- Localization available for: DE, JA (Please help to localize findbugs for your locale!)
The current release is available in the download section. This plug-in is developed and maintained by Ullrich Hafner. Please use the Hudson 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.
Adding support for new warning types
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:
- Set up your developing environment as described in the Plugin tutorial
- Check out the warnings plug-in from https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/warnings
- Run maven with the command mvn install to see if the plug-in builds before you change anything
- Add a new class YourFormatParser to the package hudson.plugins.warnings, see GccParser or JavacParser as examples
- Add a new test case YourFormatParserTest to the package hudson.plugins.warnings, see GccParserTest or JavacParserTest as examples.
- Register the new parser in the method getAllParsers() of the registry ParserRegistry
Changelog
Release 3.2
Release 3.1
- Added parser for AcuCobol warning messages (issue #5024, thanks to Jerry Shea for the patch)
- Improved MSBuild parser to also display sharepoint warnings (issue #4731)
- Fixed regular expression for GCC parser (issue #4707)
- Fixed trend report link if there are no results available yet (issue #5156)
- Fixed preview of trend reports
- Added dependency to Hudson 1.337 due to a class loader bug in previous versions (issue #4993)
Release 3.0
- Extracted common code of the static code analysis plug-ins into a new utility plug-in "analysis-core"
- Several bug fixes and small improvements
Release 1.x-2.x Changelog
