sonarqube-msbuild-runner

问题 I've a Visual Studio Team Services build definition containing a Visual Studio Build task surrounded by the Sonar Begin Analysis and End Analysis task. The Visual Studio Build packages a SharePoint provider hosted add-in using the /p:IsPackaging=True property. If this property is set I get the following error from the Sonar Build Runner: 2015-11-27T13:23:05.9534586Z WARNING: Duplicate project GUID: "31ef7995-fdbc-4307-9024-a3d640fdf987". Check that the project is only being built for a single

问题 I've a Visual Studio Team Services build definition containing a Visual Studio Build task surrounded by the Sonar Begin Analysis and End Analysis task. The Visual Studio Build packages a SharePoint provider hosted add-in using the /p:IsPackaging=True property. If this property is set I get the following error from the Sonar Build Runner: 2015-11-27T13:23:05.9534586Z WARNING: Duplicate project GUID: "31ef7995-fdbc-4307-9024-a3d640fdf987". Check that the project is only being built for a single

问题 SonarQube MSBuild runner fails if I deactivate FxCop rule in quality profile: Unable to find the rule key corresponding to the rule config key 'CA1305' in in repository "fxcop". I've bulk-added all the fxcop rules. Added a project. Then then deactivated some rules in quality profile and tried to analyze new project. Even there was NOT any violations of this rule in code - runner still fails with this weird error. 回答1: I suspect that you are somehow importing an FxCop report that contains

问题 Is there a way to programatically exclude artifacts from Sonar analysis using the MSBuild Scanner? We have a number of different Visual Studio solutions in our git repository. Almost all of these solutions make use of projects containing shared code. I am wishing to exclude code coverage from these common projects - but only for certain Sonar projects. Always excluding a project is straightforward and documented via adding a <PropertyGroup> section in the .csproj . Adding the /d:sonar

问题 I have set up a local SonarQube 5.1.1 server. I have also installed the C# plugin (version 4.1), as well as the MSBuild runner (version 1.0). I then performed two separate runs on the .NET codebase for the project I am currently working on: Using sonar-runner and the C# plugin Using the MSBuild runner Both runs were made through the CLI. However, the runs yielded very different results. Here is an example: In the first run SonarQube calculated the number of code lines to be roughly 956 000,

问题 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. 回答1: @Techtwaddle is correct: the MSBuild.Runner invokes the sonar-runner. The MSBuild.Runner v0.9 does the following: fetches configuration settings from the SonarQube server; gathers information during the MSBuild

问题 I'm trying out SonarQube using the new MSBuild SonarQube Runner v1.0. The Pre-processing works fine E:\sonarQube\MSBuild.SonarQube.Runner-1.0>MSBuild.SonarQube.Runner.exe begin /k:"MyKey" /n:"MyProject" /v:"1.0" ....... Process returned exit code 0 Pre-processing succeeded. Then MSBuild works E:\sonarQube\WebApplication2013>msbuild Microsoft (R) Build Engine version 4.0.30319.34209 [Microsoft .NET Framework, version 4.0.30319.34209] Copyright (C) Microsoft Corporation. All rights reserved. ..

问题 I am trying to migrate from the old Sonar runner to the new MsBuild Sonar runner in a .NET project. The last problem I have is doing the FxCop analysis. If the quality profile in Sonar contains any FxCop rules, I get the following build error: ERROR: Caused by: The property "sonar.cs.fxcop.assembly" must be set and the project must have been built to execute FxCop rules. This property can be automatically set by the Analysis Bootstrapper for Visual Studio Projects plugin, see: http://docs

问题 We have a private sonarqube instance setup on our infrastructure, we analyzed a project source code and see that analysis results shown in sonarqube dashboard do not include all projects as shown in VSTS code coverage results. The excluded projects aren't test projects. Details below, SonarQube version: 6.7.1, Community Edition SonarC# version: 6.8.2(build 4717) SonarQube VSTS task version : 3.2.0(4.1 version doesn't work at all) SonarScanner for MSBuild: 4.1 Solution Version: VS 2015 VSTest

问题 After upgrading to SonarQube 6.7 LTS, many of our projects started failing during " complete SonarQube analysis " task with below error: [error]java.lang.IllegalArgumentException: No FxCop analysis has been performed on this project, whereas it contains cs files: Verify that you are using the latest version of the SonarQube Scanner for MSBuild, and if you do, please report a bug. In the short term, you can disable all FxCop rules from your quality profile to get rid of this error. These