Plugin Information View CCM 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: This plugin is up for adoption. Want to help improve this plugin? Click here to learn more!
View CCM 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:
This plugin is up for adoption. Want to help improve this plugin? Click here to learn more!
This plugin 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 are also based on the aggregated results.
The CCM plug-in scans for ccm.xml files in the build workspace and reports the number of warnings found.
The current release is available in the download section. This plug-in is developed and maintained by Ullrich Hafner. Please use the 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.
For commercial support, please get contact us via @tupilabs
- Merged pull request #5 to add support to the Workflow Plug-in (Thanks to @amunis)
- Merged pull requests to add support for "graded" complexity reports. Some tools also describe complexity with "grades", like A, B, C, D, E and F. The plugin will now recognize grades and assign them priorities. The mappings are as follows: A -> low, B -> normal, C, D, E and F -> high priority.
- Merged pull requests for start and end line in the reports
- Use of analysis-core API to refactor the old code and make it compliant with standard static analysis plug-ins in Jenkins
- Instead of a builder plus a graph generator, now the plug-in is simply a publisher. It means that the plug-in won't invoke CCM anymore. You should use Windows batch commands, MSBuild or other build tools to invoke CCM.
- Due to the refactoring, the i18n for Portuguese and Spanish were lost.
- Finished Portuguese translation
- Added Spanish language support
- BUG-8165 - Failed to load hudson.plugins.ccm.CCMBuilder at hudson startup on hudson version 1.384 with current version of CCM plug-in (thanks to
abjoshi for reporting)
- BUG-8336 - When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders (thanks to Iristyle for reporting)
- Created maven site
- i18n. Now CCM supports English and Brazilian Portuguese.
- Rename class CCMBuilderDescription to CCMBuilderDescriptor to keep source code following the standard of names found in many plug-ins code.
- Add help info for all options seen by the user (the ? blue icon)
- Allow the user to define the output file name. (Not implemented)
- Remove unused class files in source code.
- Let the user define multiple source folders instead of only one.
- Let the user define multiple exclusion filters (files, folders and functions). According to CCM 1.0.2 configuration file.
- BUG-7522 - The plugin wasn't ready to behave in distributed Hudson. (thanks to svenborman for reporting and help testing)
- BUG-7531 - The execution command was compatible with Windows XP, Vista and 7, however in Windows 2003 it needed double quotes added to work out properly. (again thanks to svenborman for reporting and help testing)
- First version of the plug-in (the development was guided based on the source code of the following plug-ins: Violations, Tasks, Seleniumhq and Sonar).
- Use Area charts (like those that display test results in Jenkins for TestNG and JUnit)