-
Notifications
You must be signed in to change notification settings - Fork 52
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
Kover exclude rules in Sonarqube scan #156
Comments
Hi, |
Thanks @shanshin for clarifying. Will there be plans to support full integration with analysis tools like Sonarqube? |
There are no short-term plans for integration with Sonarqube, but it will be added as soon as the plugin and the IntelliJ Coverage Engine are implemented to a stable state. |
@johnryM with the property you mentioned above you will afaik exclude the files from sonar completely (coverage + static analysis). To just exclude them from coverage you need to use this property:
Edit: We need to do the same when using Jacoco reports, so I guess it's just the intended sonarqube behavior that you need to define the exclusions twice. |
@sarn0ld In the end we went with your solution. I didn't know it was the same process with Jacoco as well. Thanks for letting me know! |
Duplicates #268 |
I'm using Kover in my Android Project to generate the xml report that's sent to my Sonarqube server.
I would like to exclude all Kotlin classes that are inside a "di" folder but my Kover exclude rules don't seem to work.
My package structure is
My merged report gradle config is
When I run my sonarqube scan. The module files in the various DI folders are visible in the coverage report
Defining "sonar.exclusions property" in my build gradle file does solve this issue
Is this the correct way of excluding files in the final sonarqube report or is possible to perform the same exclusions by just configuring the Kover merged reports?
The text was updated successfully, but these errors were encountered: