[jbosstools-issues] [JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935525#comment-12935525 ] 

Mickael Istria commented on JBIDE-16214:
----------------------------------------

> Yes we use jacoco jenkins plugin for code coverage
Ok. I don't know how to have it working for the Jenkins plugin. The script I've written dynamically computes the list of jars to use by reading surefire configuration. This cannot be achieved by the Jenkins plugin, it would require to rewrite another Jenkins plugin.
On the Jenkins instance, we have an extra build step running the (currently Ant-based) script that generates HTML report, and we use the Jenkins Link plugin to add a link to the reports.

> Yes we publish code coverage results to sonar. It's requested by management
Ok, That's cool. How are Sonar reports behaving? Do they reports accurate metrics? Not sure it will be able to bind classes, and I don't know what we can do with it.

A general solution could be that Tycho avoids using the pack200 jars. http://dev.eclipse.org/mhonarc/lists/tycho-user/msg05194.html However, I couldn't get much help on this topic.


About the multiple class issue, I'll try to reproduce the scenario you describe and find whether there's something that can be done in the script. But IMO, the solution is more to fix jars to avoid multiple class definition than tweaking the script to workaround this bad practice.
                
> Code Coverage jobs needs to have locally available measured plugins
> -------------------------------------------------------------------
>
>                 Key: JBIDE-16214
>                 URL: https://issues.jboss.org/browse/JBIDE-16214
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.1.1.CR1
>            Reporter: Vlado Pakan
>            Assignee: Mickael Istria
>             Fix For: 4.1.x
>
>
> Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site.
> When these are built locally prior to build calculating code coverage it returns correct results.
> Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build.
> We need to find way how to fix this.
> It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira