View Warnings on the plugin site for more information.
Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:
Jenkins' Warnings plugin collects compiler warnings or issues reported by static analysis tools and visualizes the results. The plugin (and the associated static analysis plugin suite) has been part of the Jenkins plugin eco-system for more than ten years now. In order to optimize user experience and support Pipeline, a major rewrite of the whole set of plugins was necessary. This new version (code name White Mountain) is now available as a public beta. Please download and install this new version and help us to identify problems before the API is sealed.
The new release is available in the experimental update center. It has built-in support for almost hundred static analysis tools (including several compilers), see the list of supported report formats.
The Warnings plugin provides the following features when added as a post build action (or step) to a job:
The plugin scans the console log of a Jenkins build or files in the workspace of your job for any kind of issues. There are almost one hundred report formats supported. Among the problems it can detect:
errors from your compiler (C, C#, Java, etc.)
warnings from a static analysis tool (CheckStyle, StyleCop, SpotBugs, etc.)
duplications from a copy-and-paste detector (CPD, Simian, etc.)
open tasks in comments of your source files
The plugin publishes a report of the issues found in your build, so you can navigate to a summary report from the main build page. From there you can also dive into the details:
distribution of new, fixed and outstanding issues
distribution of the issues by severity, category, type, module, or package
list of all issues including helpful comments from the reporting tool
annotated source code of the affected files
trend charts of the issues
In the documentation of the plugin (now part of the GitHub project), I’ll show the new and enhanced features in more detail.