Skip to content
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 lost after upgrading from version 2.8 to 3.0 #93

Closed
octopus-prime opened this issue Sep 27, 2020 · 2 comments
Closed

coverage lost after upgrading from version 2.8 to 3.0 #93

octopus-prime opened this issue Sep 27, 2020 · 2 comments

Comments

@octopus-prime
Copy link

This commit
b93205f
shows that upgrading to version 3.0 is just changing the number.

So i did. But after upgrading the coverage drops from 100% to 0%.
See octopus-prime/zero@601f0f8
and https://sonarcloud.io/dashboard?id=octopus-prime_zero

What did i miss??

@sylvain-combe-sonarsource
Copy link
Member

Hello @octopus-prime
if you don't have a SonarSource support subscription, the best way to get help with any SonarSource Code Quality and Security tool(SonarCloud, SonarQube and the scanners) is with SonarSource community forum.
This said I can give you a hint here with the gradle scanner 3.0 release notes.

Have a good day!
Sylvain

@octopus-prime
Copy link
Author

Thanks @sylvain-combe-sonarsource for your hint.
Remove the implicit dependency between 'sonarqube' task and 'test'
That information i was looking for - works like a charm now :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants