{"id":26485,"date":"2016-12-13T12:28:31","date_gmt":"2016-12-13T20:28:31","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=26485"},"modified":"2019-02-14T15:55:57","modified_gmt":"2019-02-14T23:55:57","slug":"sonarsource-have-announced-their-own-sonarqube-team-services-tfs-integration","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/sonarsource-have-announced-their-own-sonarqube-team-services-tfs-integration\/","title":{"rendered":"SonarSource have announced their own SonarQube Team Services \/ TFS integration"},"content":{"rendered":"

Microsoft have been partnering with SonarSource for almost two years to bring SonarQube to .NET developers and to make it easy to analyze MSBuild and Java projects from Visual Studio Team Services, TFS and Visual Studio. The partnership, and Team Services extensibility, have now matured to the point that we have jointly decided that it was time for Microsoft to transfer ownership of the SonarQube MSBuild build tasks to SonarSource. They are better placed to keep the tasks up to date and consistent with the SonarQube vision. SonarSource have now announced<\/a> the availability of their own SonarQube Team Services and TFS extension on the VSTS marketplace.<\/p>\n

Concretely what does it change for you?<\/h4>\n

In the past, we released the SonarQube Team Services build tasks \u201cin the box\u201d, so whenever we updated VSTS \u2013 every 3 weeks \u2013 we pushed updates to these tasks. The tasks were also shipped with the TFS on-premises product. The source code is in the vsts-tasks<\/a> repository on GitHub along with the other tasks released by Microsoft. In future Microsoft’s SonarQube tasks won’t be released in the service or TFS product. Like many partners, SonarSource is now providing a dedicated SonarQube extension<\/a>. This allows them to fully control the development and deployment of updates and fixes. Therefore, we are deprecating the MSBuild SonarQube tasks, and you will need to install the SonarQube extension to continue analyzing technical debt in your MSBuild projects.<\/p>\n

What build tasks are affected?<\/h4>\n

The two tasks which are deprecated are the SonarQube for MSBuild tasks (SonarQube for \u2018MSBuild \u2013 Begin Analysis\u2019 and \u2018SonarQube for MSBuild \u2013 End Analysis\u2019).<\/p>\n

Note that we also integrated SonarQube into the Java build tasks for Maven and Gradle in order to enable code analysis feedback in Pull Requests. These integrations will remain as they are for now, and will continue to be released by Microsoft. SonarSource may in the future provide a replacement build task or tasks for Java with this capability.<\/p>\n

What will be the deprecation experience?<\/h4>\n

If you are a Team Services user, when you run a build that contains SonarQube for MSBuild tasks, you\u2019ll notice some build warnings:<\/p>\n

\"clip_image002\"<\/a><\/p>\n

The warnings contain hyperlinks that will help you migrate.<\/p>\n

Also, if you try to add the former tasks to a build definition, you\u2019ll notice the [DEPRECATED] prefix in their label:<\/p>\n

\"clip_image003\"<\/a><\/p>\n

On the other hand, if you are working on-premises with TFS 2017, you\u2019ll see these changes starting with TFS 2017 Update1.<\/p>\n

Moving to the new tasks<\/h4>\n

At some point, the Microsoft-owned tasks will be deleted. We recommend switching to SonarSource\u2019s extension as soon as possible. This is straight-forward \u2013 just install the SonarQube extension<\/a> to your account and you\u2019ll notice three new tasks in your library:<\/p>\n

\"clip_image004\"<\/a><\/p>\n

You\u2018ll recognize the last two, but the first is new: SonarSource is introducing a new task named \u201cSonarQube Scanner CLI<\/a>\u201d that supports analysis of projects outside MSBuild and Java build technologies, a common request. You can now analyze your node.js projects, etc \u2026<\/p>\n

Minor breaking changes<\/h4>\n

SonarSource have taken the opportunity to address shortcomings in the old tasks and to action some of your feedback. Consequently, there are 2 small breaking changes:<\/p>\n