Warnings Plugin

Added by Ulli Hafner, last edited by Ulli Hafner on May 13, 2009  (view change)
Hudson
Home
Downloads
Mailing lists
Source code
Issue tracker
#
Commercial Support
Documents
Meet Hudson
Use Hudson
Extend Hudson
Plugins
SCMs
Triggers
Build Tools
Build Wrappers
Notifiers
Reporters
Ext. Site Integration
Uploaders
Misc
Others
Container-specific Notes
Site Map

This plugin generates the trend report for compiler warnings in the build log  

Description


 
The Warnings plug-in scans the build log 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) 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)
  • Localization available for: DE (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.

Changelog

Release 2.8

  • Added new trend graphs and a configuration screen per job or per user.
  • Fixed module detection if the plug-in parses warnings from several files (issue #3620).
  • Added an option to skip the console log and to parse only the warnings in the specified set of files (issue #3339).
  • Added support for MSBuild parser error messages (issue #3582).

Release 2.7

  • Improved computation of new warnings detection (report)
  • Added Japanese localization (thanks to Itou Akihiro!)

Release 2.5

  • Added configuration option to invoke the plug-in for failed builds (issue #3327).
  • Fixed build health reporting and failure thresholds for native m2 builds (issue #3310).

Release 2.4

  • Added support for another type of Pc-Lint warnings

Release 2.3

  • Added support of IAR and PcLint warnings (Thanks to Claus Klein for the patch)
  • Added build status thresholds: now you can set the build status to unstable or failure if the total number of the number of new warnings exceeds the defined thresholds (issue #2537, issue #3024).
  • Improved new warning detection: now warnings are only considered as new if the associated source code context (3 lines of code) differs.

Release 2.2

  • Added validation of file pattern in configuration screen

Release 2.1

  • Fixed priority evaluation radio buttons in configuration screen (issue #2805)

Release 2.0

  • Added new configuration entry "default encoding" that is used when the plug-in reads or parses files (issue #1999)
  • Added configuration option to specify the actual warnings parsers (issue #2462). This fix should also reduce the memory footprint and execution time (issue #2660).
  • Guess the Ant or Maven module names when scanning the files (issue #2657).

Release 1.x Changelog

Labels

  Edit Labels