I checked sonarqube has support for detekt (I want to totally remove the sonar original issues and use detekt reports, or in other words, I want a GUI to see detekt issues + codecoverage via sonarqube. https://docs.sonarqube.org/latest/analysis/external-issues/
In another hand, I have seen there is a sonar-detekt plugin. With the official property is not enough so I need to use this plugin? What are the differences?
g
gammax
12/15/2021, 2:48 PM
We’re lacking capacity to do proper Sonarqube maintainance. If you’re willing to help us with https://github.com/detekt/sonar-kotlin that would be more than appreciated ❤️
I’m unsure what are the differences between the two (I was not even aware Sonarqube has 1st party Detekt support).
j
Javier
12/15/2021, 2:51 PM
Not sure if there are someone from Sonarqube in this Slack to know if we got the same value from their implementation and sonar-kotlin plugin, if so, one less thing to maintain 🙂
g
gammax
12/15/2021, 3:27 PM
From my experience, folks on sonarqube are extremely slow to respond + they have their own forum where you need to subscribe
j
Javier
12/15/2021, 3:27 PM
I will try to ask anyway
🙏 1
s
schalkms
12/15/2021, 7:23 PM
I think the following issue outlines the 2 options.
I guess you have two options:
Either use the official sonarqube Kotlin plugin and publish detekt reports via `property "sonar.kotlin.detekt.reportPaths", "${project.buildDir}/reports/detekt/detekt-report.xml".
Or use both our and sonarqube's plugin together with a joint quality profile and detekt.sonar.kotlin.config.path.