Plugin needs critical update

[danieljimenez]

This is languishing for an advertised plugin, it should be moved to use sonar-scanner instead of sonar-runnner, and needs to be updated to no longer ask for JDBC connection information.

[Linfar]

@danieljimenez the plugin uses SonarQube Scanner. It is located under sonar-runnner directory due to backward compatibility reasons. The same is for JDBC connection information.
We plan to switch TeamCity SonarQube plugin to use new Tools functionality introduced in TeamCity 10. This will allow to select needed Scanner version manually as well as uploading new ones and will solve location.
Speaking of JDBC connection info the only I can do is hide these fields.

[danieljimenez]

It's still a very, very old version. I ended up using this fork, and then manually updating the scanner libraries: https://github.com/MikhailKaduchka/TeamCity.SonarQubePlugin

[asbrown77]

Year on from above report and plugin still using a very old sonar-runner version 2.4. This needs to be updated as this version runner, now called scanner, no longer supports sonarqube 6.7.2 or above. Therefore this useful plugin is no longer a viable option if using the new version of sonarqube. That said the scanner for msbuild works fine as underlying scanner is a newer version (3.0).

[Linfar]

@asbrown77 @danieljimenez The latest plugin version is bundled with SonarQube Scanner v3.0.3 which could be set as default in Administration -> Tools page or in the Build Step itself. It's also possible to easily upload custom versions.