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 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.

• 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, Oracle Invalids, Doxygen, Robocopy, Perforce, Cobol, PHP, Flex
• 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:

1. Set up your developing environment as described in the Plugin tutorial
2. Check out the warnings plug-in from https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/warnings
3. Run maven with the command mvn install to see if the plug-in builds before you change anything
4. Add a new class YourFormatParser to the package hudson.plugins.warnings, see GccParser or JavacParser as examples
5. Add a new test case YourFormatParserTest to the package hudson.plugins.warnings, see GccParserTest or JavacParserTest as examples.
6. Register the new parser in the method getAllParsers() of the registry ParserRegistry

Changelog

Release 3.10

• Fixed links to source files with relative paths (issue #7184, issue #7134, issue #3488)
• Fixed persistence of generic parsers (issue #7259)

Release 3.9

• Fixed parsing of multi-line Eclipse warnings (issue #7077)

Release 3.8

• Added a new generic parser that can be configured in the UI to enable parsing of project specific warning messages without the need of extending the plug-in (issue #3895).
• Fixed ant links (issue #6862)
• Fixed parsing of multi-core build with MS Build (issue #6709)
• Fixed parsing of doxygen 1.7.1 messages (issue #6971)
• Fixed computation of module names for maven projects (issue #6768)
• Don't report an error message if a maven module does not contain a report file (issue #6895)

Release 3.7

• Fixed naming of maven modules (issue #6513)
• Group files by path if there is no package or namespace found (issue #6698)

Release 3.6

• Improved performance of all parsers (issue #5185) (thanks to Frederic Chateau)
• Added new parsers for Doxygen, Robocopy, Perforce, NXP Coolflux DSP (thanks to Frederic Chateau, Bruno Matos, Vangelis Livadiotis, Adrián Deccico, for the patches)
• Several bug fixes (issue #6563, issue #6532, issue #6513, issue #6466, issue #6427, issue #6416, issue #6089, issue #6427, issue #3525)

Release 3.5

• Added trend graph portlets for the dashboard view
• Added option to start the plug-in even for failed builds (issue #6117)
• Added 'enlarge' link for trend graphs that shows a detail page with the graph
• Fixed ordering of warnings in detail views (issue #6132)
• Fixed warning distribution graph in files detail view (issue #6139)

Release 3.4

• Added new parsers for GCC 4 warnings (gcc and ld) (thanks to fchateau for the patch, issue #6089, issue #5870, issue #5445, issue #5606, issue #5605, issue #5671, issue #5753)
• Improved copying of remote files to master (issue #3488)
• Added a portlet for the dashboard view

Release 3.3

• Added parser for PHP warnings (thanks to Shimi Kiviti for the patch)
• Added parser for Flex SDK warnings (thanks to Vivien Tintillier for the patch)
• New warnings computation is now based on the current build and the reference build (i.e., the last successful build, see issue #5147)
• Visualized plug-in build status (based on the healthiness thresholds)
• Added high scores for successful builds
• Improved warnings detection for the Intel C++ compiler 11.1 (issue #5402)
• Fixed handling of arrays in warning messages (issue #5868)
• Don't show project action if there are no warnings (issue #5473)
• Don't show trend graph configuration on job creation (issue #5294)
• Improved remote API, now the warning keys are also exposed (issue #5195)

Release 3.2

• Added support for the new plug-in Static Analysis Collector plug-in to provide combined trend graphs and health reporting (issue #3320)
• Improved remote API, now the warnings are also exposed (issue #5195)

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