The Gradle build task now supports SonarQube analysis
SonarQube analysis for Java
In October, we updated the Maven task to support SonarQube analysis (See The Maven build task now simplifies SonarQube analysis). This time, we are pleased to announce an updated Gradle task which makes it easy for Java developers using Gradle to trigger a SonarQube analysis in Visual Studio Team Services.
Using the Gradle task with SonarQube
Just as for Maven, we have added a Code Analysis section in which you can now check the “Run SonarQube Analysis” checkbox, which then shows more options.
You will need to provide:
– The service endpoint describing your SonarQube server and credentials
– The project name, key and version (contrary to Maven, where these are mandatory properties in pom files, in Gradle these are not always present)
You can also further customize the analysis either by passing SonarQube settings via options or by chaining your Gradle config. For more information about SonarQube analysis using Gradle see http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Gradle
Limitations, Feedback and Troubleshooting
Currently this feature works only in Team Services with the Linux agent. It is not available on TFS 2015, but will be in the next major version of TFS.
We’d like to hear from you, Please Raise issues and suggestions on the issues tab of the VSTS task repository in GitHub: https://github.com/microsoft/vsts-tasks/issues