The build pipeline should look as follows now… Drag the Begin Analysis task to before the Build solution step and the end analysis task to after the unit test execution task. From the Build tab Add the task ‘SonarQube for MSBuild - Begin Analysis’ and ‘SonarQube for MSBuild - End Analysis’ task. The build template adds a bunch of tasks to the newly created build definition.Ĭlick on the + Add build step link. Choose the ‘Visual Studio’ build template. Click the + icon to create a new build definition. Launch Visual Studio Team Services and navigate to the Build Hub. Configuring SonarQube Analysis in a build pipeline Once you have added the firewall exception to allow communication from SonarQube to VSTS Agent and visa versa on TCP port 9000, launch cmd on both the machines and telnet on port 9000 to validate the channel. Since SonarQube is currently configured on port 9000, the firewall rules need to be ammended on both SonarQube server and VSTS Agent to allow communication between the two boxes on TCP port 9000. For VSTS Build Agent to consume SonarQube endpoint for code analysis, the Agent needs access to SonarQube. The VSTS Agent is set up on another virtual machine. SonarQube is setup using a single VM configuration where both the web server and the database are on one single machine. If you intent to use the hosted agent in VSTS, then you don’t need a machine with VSTS Agent set up. If you do not have Java installed on the Agent, expect to see the following error message… SonarQube requires that the Visual Studio Agent has Java installed.

If you don’t already have a build agent configured on a seperate VM, then follow the instructions to set up a VSTS Agent. The blog post also requires that you have a VM set up with VSTS Build Agent. This blogpost builds on top of that, if you don’t have a SonarQube server configured yet, follow the instructions here before moving forward. In the last blogpost we set up a SonarQube with SQL Server (Win Auth) from scratch. We’ll then look at the code analysis results summary in VSTS and see the build version mapping between VSTS and SonarQube. In this blogpost we’ll learn how to expose SonarQube endpoint to Team Build in VSTS and run a full code analysis cycle as part of the continuous integration pipeline.

Sonarqube analysis