[jbosstools-issues] [JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack200)
Dmitrii Bocharov (JIRA)
issues at jboss.org
Fri Sep 15 07:08:00 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitrii Bocharov updated JBIDE-24903:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1567, https://github.com/jbosstools/jbosstools-base/pull/597 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1567)
> Sonar: report correct test coverage (by using a build that does not use pack200)
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-24903
> URL: https://issues.jboss.org/browse/JBIDE-24903
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: build, sonar, test, test-coverage
> Fix For: 4.5.x
>
> Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png
>
>
> Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8%
> !image-2017-08-29-14-07-45-069.png!
> According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29%
> !image-2017-08-29-14-11-01-604.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list