-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverage is sometimes reported, sometimes not. #14
Comments
I guess that you are experiencing the same issue as #8 The issue is that there is a dtd in the xml report for the coverage. When using the docker image, you do not have access to internet, thus the xml file cannot be validated with the online dtd. We added a property which should fix this:
|
I've tried dtdVerification=false, it's ignored anyway. |
Ok it's strange. |
Hi, |
Having the same issue. Generating coverage.xml correctly and I do see the xml getting parsed in the command line but its not displaying in the sonarqube UI. @thibaultfalque |
hi @sogajeffrey The logs will be long so you can publish them with https://gist.github.com/. Thanks. |
No we dont use -X. Yes we build in docker. https://gist.github.com/sogajeffrey/fac8a714b4c2cf8b73bfa36240690654 |
Hi @sogajeffrey
So the coverage report is found but there is a problem with the file "cf.go". C |
@thibaultfalque Yes the file exists.
|
hi, |
Can you rerun with the new version 1.2.10-beta ? sonar-scanner -X and post the logs |
OK I understand why the file is not found but it's very strange. But when I get the path when parse the file I obtain: @danielleberre any idea why this line return a bad value ? |
@thibaultfalque I generated the coverage.xml on my local and posted it but the file that is parsed in the latest gist is from jenkins so the path is different |
So jenkins use the local coverage ? |
@thibaultfalque I generate the coverage at build time. I dont check the coverage report into the codebase. |
Please test 1.2.10-gamma |
@thibaultfalque https://gist.github.com/sogajeffrey/144e002a2c8af5322dc6169fa4bdbf3d No dice... still not working |
@thibaultfalque this is my report.xml https://gist.github.com/sogajeffrey/d37567ec3ff08694b36774aa394a9f1c |
@thibaultfalque Are we still unable to fix this? |
It's fixed now for me
…On Sat, Dec 2, 2017, 6:15 AM Daniel Le Berre ***@***.***> wrote:
@thibaultfalque <https://github.com/thibaultfalque> Are we still unable
to fix this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIa4AdKdQOJAuW1eSKHA5gjI2zNUAQqZks5s8VuQgaJpZM4N8h7s>
.
|
@f-sys could you check with the last release and close the issue if the problem is resolved ? |
@f-sys could you check with the last release and close the issue if the problem is resolved ? |
Description
When golang coverage is generated locally and sonar-scanner is launched locally it reports coverage measures to sonarqube. When it is launched in docker environment via Gitlab CI, it doesn't report coverage. Golang xml files are same, sonar-scanner scans vendor folder, but it is excluded.
Steps to Reproduce
Content of your sonar-project.properties
Log of sonar-scanner related to the plugin
Versions
SonarQube: 6.4 (build 25310)
SonarQube Scanner: 3.0.3.778
sonar-golang: 1.2.8
Java: 1.8.0_51 Oracle Corporation (64-bit)
Linux: 3.16.0-4-amd64 amd64
Additional Information
gitlab.kancelar.seznam.cz/Odpovidac/iris-firmy/handler/coverage.xml
coverage.zip
Succesfull local log:
scanner.zip
The text was updated successfully, but these errors were encountered: