Using in pipeline - standalone Sonar Scanner versus Sonar Scanner Maven plugin
Opened this issue · 0 comments
The readme for this plugin says to use the standalone Sonar Scanner binary. I've configured my Jenkins pipeline according to the SonarQube documentation and use the Sonar Scanner Maven plugin to run the Sonar scans. I cannot find any evidence that this plugin executed when the Sonar Scanner Maven plugin executed its inspections. For example, I can see that the Dependency-Check plugin executed:
[INFO] Sensor Dependency-Check [dependencycheck] (done) | time=5ms
So, does usage of this plugin require the standalone Sonar Scanner, or can this plugin be made to work with the official Sonar Scanner for Maven? If this plugin can be made to work with the Maven plugin, what needs to be done to make it work? I've installed the plugin, configured the location for the shellcheck
binary, and assigned the Shellcheck quality profile to an SQ project, but I don't see the plugin working yet.
Thanks for your help!