To get even more info out of it and get some kind of a deeper overview on the status of the package right after a build without any manual interaction, I developed a plugin to be able to use the Codescanner tool within hudson.
CodeScanner is a static source code analysis tool for Symbian programs written in C++. Static analysis tools delve deep into code, exploring line by line for the sources of defects. CodeScanner is specifically for use with Symbian code. As well as identifying C++ coding convention deviations, CodeScanner identifies incorrect descriptor usage, cleanup stack errors, UID clashes, and other subtle problems that are hard to track down.
There are several exciting features available in the plugin:
- 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
- Detail reports of the found warnings optionally filtered by severity (or new and fixed)
- Short messages is read from the report file
- 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
For more information, installation instructions and how to use the plugin, have a look at the wiki page: CodeScanner Plugin
A huge thank you to Ulrich Hafner, author of several similar static analysis hudson plugins. The codescanner plugin uses his analysis-core classes as a base, this is were most of the magic happens. Using his work, this plugin was easy and fast to write.
