[
https://issues.jenkins-ci.org/browse/JENKINS-13170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161357#comment-161357 ]
Bruno P. Kinoshita commented on JENKINS-13170:
----------------------------------------------
Hi again Samuele!
I've refactored CCM Plug-in to be used like other static analysis plug-ins (
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins).
As a result of this change, the plug-in now is not a Builder anymore, but a Publisher. It means, basically, that the plug-in is not invoked during the build anymore, but after all the build steps have finished. So now you have to use MSBuild, or add a Windows batch command to invoke CCM, and output in XML. Then enable CCM.
However, the bright side of this is that the UI is the same as PMD, Tasks, FindBugs and other plug-ins configured using analysis-core (yup, you have to install this one first, I know it can be inconvenient, but it's worth :).
There are more graphics in the dashboard available now, as well as better organization of results.
Could you give it a try again?
Sorry for taking this decision without letting you know first. I created CCM plug-in before the analysis-core and other static analysis plug-ins were released, and it was my first plug-in. That's why I had to do such change.
Thank you!
Bruno
> JellyTagException when clicking on CCM trend chart
> --------------------------------------------------
>
> Key: JENKINS-13170
> URL:
https://issues.jenkins-ci.org/browse/JENKINS-13170> Project: Jenkins
> Issue Type: Bug
> Components: ccm
> Affects Versions: current
> Environment: Ubuntu
> Reporter: Samuele Gantner
> Assignee: Bruno P. Kinoshita
> Attachments: screenshot.png, stacktrace.txt
>
>
> When trying to click on the CCM chart, the resulting page has 500 status code.
> org.apache.commons.jelly.JellyTagException: file:/var/lib/jenkins/plugins/ccm/WEB-INF/classes/hudson/plugins/ccm/CCMProjectAction/nodata.jelly:5:64: <st:include> No page found 'sidepanel.jelly' for class hudson.plugins.ccm.CCMProjectAction
> Exception and screenshots are attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspaFor more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
