SonarQube Runner和SonarQube.MSBuild.Runner之间的关系

本文介绍了SonarQube Runner和SonarQube.MSBuild.Runner之间的关系的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

关于SonarQube的公告与MSBuild和Team Build集成后，任何人都可以就SonarQube Runner和SonarQube.MSBuild.Runner之间的关系提出建议吗?我不清楚SonarQube.MSBuild.Runner是替换 SonarQube Runner还是位于它上面.

Regarding the announcement of SonarQube integration with MSBuild and Team Build, can anyone advise on the relationship between SonarQube Runner and SonarQube.MSBuild.Runner? I'm unclear whether SonarQube.MSBuild.Runner replaces SonarQube Runner or whether it sits on top of it.

推荐答案

@Techtwaddle是正确的:MSBuild.Runner调用声纳运行器.

@Techtwaddle is correct: the MSBuild.Runner invokes the sonar-runner.

MSBuild.Runner v0.9执行以下操作:

The MSBuild.Runner v0.9 does the following:

• 从SonarQube服务器获取配置设置；
• 在MSBuild阶段收集信息；
• 生成一个sonar-project.properties文件；
• 调用声纳运行器进行进一步分析.

现在在致电声纳运行器之前执行了一些分析.例如，FxCop分析现在作为MSBuild阶段的一部分进行，而不是从声纳运行器中调用.

Some of the analysis is now performed before calling the sonar-runner. For example, FxCop analysis is now happens as part of the MSBuild phase rather than being invoked from the sonar-runner.

当前，您必须手动安装声纳运行器和MSBuild.Runner.计划通过工作来更改此设置，因此您只需要安装MSBuild.Runner.参见 jira.sonarsource/browse/SONARMSBRU-42 .

Currently, you have to manually install both the sonar-runner and the MSBuild.Runner. Work is planned to change this so you will only need to install the MSBuild.Runner. See jira.sonarsource/browse/SONARMSBRU-42.