The static code analysis plug-ins are being maintained by their owner from a new home. The plug-ins are still compatible with Hudson, however, the entry points for documentation and issue reporting have been combined in order to provide a single point of entry.
This plugin scans the workspace files for open tasks and generates a trend report.
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.
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 tasks scanner plug-in scans the workspace files for open tasks like TODO, FIXME, or @deprecated. It is inspired by the maven taglist plug-in. This plug-in is part of the suite of static code analysis plug-ins that are documented on a separate WIKI page.
- You can specify the files to scan after a build
- Three configurable priority levels are supported (e.g. HIGH=FIXME, NORMAL=TODO, LOW=@deprecated)
- Several trend reports showing the number of tasks per build
- Overview of the found tasks per module or package
- 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 tasks filtered by severity
- Colored HTML display of the corresponding source files and with direct links to the tasks
- Highlighting of the line that contains a task (with a tool tip showing the priority)
- 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 findbugs:findbugs or site)
- Remote API to export the build quality and found open tasks
- Localization available for: DE, JA (Please help to localize task scanner for your locale!)
Configuring the plugin should be self-explanatory: You simply need to activate the task scanner plugin as shown below. Add the tag keywords you would like to use and save the configuration. Then the next build will report the number of open tasks and show the trend.