Most of the Jenkins publishers (test results, warnings, etc.) assume that the project builds a single target, so you will have trouble if you build multiple targets in a single project. Even though you have a large number of targets, it may be better to have separate projects for each one (you can use templating plugins to manage the proliferation of projects with nearly identical settings).
----- Original Message ----- From: [email protected] To: [email protected] At: Apr 25 2014 05:32:03 Hi All, I've got a jenkins job that builds around 30 targets. As part of the build, cppcheck gets executed over the source of each target and I end up with one xml file per target. A jenkins post build action publishes the cppcheck reports. There are two issue I have: 1. Since all the reported issues are combined into a single table by the CppCheck plugin, it isn't clear which target has the issue. A source file can be shared by multiple targets but the targets have different build configurations. 2. Some existing issues are simultaneous reported as fixed and unchanged in the CppCheck Result details table. This is not due to differences in build configurations. I suspect this is due to the way the xml reports are combined and compared with previous results? If an existing issue is reported as unchanged n times, it also get reported as solved n-1 times. So I feel I'm probably not using the CppCheck as intended. Does anyone have a better suggestion for how I should manage running cppcheck over multiple targets and reporting the results? Regards Mavik -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. ------------------------------------------------------------------------------- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
