-
Notifications
You must be signed in to change notification settings - Fork 24
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
Clover sensor not firing for groovy projects #44
Comments
Here are the relevant bits of Gradle sonarqube config from my build script (I'm using version 2.8 of the 'org.sonarqube' gradle plugin and have also tried 3.0 with the same results):
|
This seems to be related to Groovy projects only. Coverage on Java projects is being imported properly, so I'm going to close this ticket out. |
Hi, I reopen this issue to keep a track on what we are doing : but since the 4.2 release is focus on this bug fix, I think that we should fix it before releasing 😅 |
This is not really a bug report, but I'm not sure where else to post my question...
I have been unable to figure out why one of my projects is not importing the Clover coverage into SonarQube EE (8.5.0).
I am setting the sonar.clover.reportPath property (see screenshot) and the file is present/valid. However, I am getting the following message when I run my (Gradle) SonarQube scan with debug-level logging:
'Clover Coverage Analysis' skipped because there is no related file in current project
So what am I missing? What files/properties are needed to make the Clover sensor fire?
I can provide logs, scanner context, etc., but I'm not sure what would be valuable at this point. Any assistance is appreciated.
The text was updated successfully, but these errors were encountered: