sonarqube-msbuild-runner

SonarQube: File is not under the project directory

Deadly 提交于 2019-12-11 10:27:41
问题 I have a lot of warnings when I run the MSBuild.SonarQube.Runner. They are in the format: EXEC : warning : File is not under the project directory and cannot currently be analysed by SonarQube. File: [file], project [project] I found the post about this problem. However the solution does not apply to my problem. There is no occurrence of Test anywhere in my path. I have been using SonarQube 5.1.2 and Sonar-MsBuild-Runner 1.0.1. In the hope so see an improvement, I tried Sonar-MsBuild-Runner 1

SonarQube msbuild runner does not import all fxcop messages

最后都变了- 提交于 2019-12-08 10:04:59
问题 We use sonarqube and the sonarqube msbuild runner in our TFS vNext builds. The integration works: we see new analysis results in sonarqube as expected. However, not all issues from the CodeAnalysisLog.xml are imported in sonarqube. If we run the analysis locally, those issues are reported. If we inspect the CodeAnalysisLog.xml as produced on the build server, the issue is present in the file. SonarQube however does not show it. We do use custom rule-sets, but everything is configured

MSBuild SonarQube runner skipping auto-generated files?

两盒软妹~` 提交于 2019-12-06 04:33:52
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, while in the second run it was calculated to be "only" about 434 000. I then did some digging, and it

How to make Sonarqube exclude a .NET (C#) project from coverage measures

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-04 22:56:51
问题 Sonarqube allows for individual files to be excluded from code coverage by adding patterns in the sonar.coverage.exclusions key. This can be done on a project level by adding them in the UI and even in a .csproj file by specifying a SonarQubeSetting element. I.e. <SonarQubeSetting Include="sonar.coverage.exclusions"> <Value>**/*.cs</Value> </SonarQubeSetting> However, both of these approaches don't seem to work. Playing with the patterns, as specified in the SonarQube documentation doesn't

How to make Sonarqube exclude a .NET (C#) project from coverage measures

一个人想着一个人 提交于 2019-12-03 13:39:45
Sonarqube allows for individual files to be excluded from code coverage by adding patterns in the sonar.coverage.exclusions key. This can be done on a project level by adding them in the UI and even in a .csproj file by specifying a SonarQubeSetting element. I.e. <SonarQubeSetting Include="sonar.coverage.exclusions"> <Value>**/*.cs</Value> </SonarQubeSetting> However, both of these approaches don't seem to work. Playing with the patterns, as specified in the SonarQube documentation doesn't provide the desired result. I'm also aware of the existence of the SonarQubeExclude MSBuild property, but

Migrating from sonar-runner to MSBuild Runner. Where did the sonar-project.properties file go?

﹥>﹥吖頭↗ 提交于 2019-12-01 11:13:24
Scenario: I am migrating our current VS Solution analysis setup from using the sonar-runner to using the MSBuild runner. However I am encountering a fairly significant problem. In the old setup, we specified our project name, key and most importantly a long list of skipped projects ( sonar.visualstudio.skippedProjectPattern ) using the sonar-project.properties file. This is because [WARNING: ugly legacy bad coding practice alert] we have six solutions that build dozens and dozens of projects, all out of the same git repo. A lot of the projects are common across several solutions and we don't

Migrating from sonar-runner to MSBuild Runner. Where did the sonar-project.properties file go?

倖福魔咒の 提交于 2019-12-01 08:17:44
问题 Scenario: I am migrating our current VS Solution analysis setup from using the sonar-runner to using the MSBuild runner. However I am encountering a fairly significant problem. In the old setup, we specified our project name, key and most importantly a long list of skipped projects ( sonar.visualstudio.skippedProjectPattern ) using the sonar-project.properties file. This is because [WARNING: ugly legacy bad coding practice alert] we have six solutions that build dozens and dozens of projects,

MSBuild SonarQube runner in command line

你说的曾经没有我的故事 提交于 2019-12-01 01:16:07
I have a problem analyzing a project using MSBuild SonarQube runner. SonarQube database and server are up and running, i have tried to analyze an example project and it all went well. But when i try to analyze my project something goes wrong. The analysis completes with no errors but no analysis data is saved to database, no issues, no lines of code count, nothing. Anyone has any idea of what could be wrong? EDIT: sonar-project.properties: sonar.projectKey=shrooms sonar.projectName=Shrooms sonar.projectVersion=1.0 sonar.sources=. sonar.properties: sonar.jdbc.username=user sonar.jdbc.password

MSBuild SonarQube runner in command line

不想你离开。 提交于 2019-11-30 21:30:47
问题 I have a problem analyzing a project using MSBuild SonarQube runner. SonarQube database and server are up and running, i have tried to analyze an example project and it all went well. But when i try to analyze my project something goes wrong. The analysis completes with no errors but no analysis data is saved to database, no issues, no lines of code count, nothing. Anyone has any idea of what could be wrong? EDIT: sonar-project.properties: sonar.projectKey=shrooms sonar.projectName=Shrooms

Excluding projects from the MSBuild Runner without changing csproj files

不打扰是莪最后的温柔 提交于 2019-11-30 18:34:10
问题 Using SonarQube 5.2 (MSBuild.SonarQube.Runner.exe)... Given a Visual Studio solution containing 10 C# projects, is it possible to exclude half of those projects from SonarQube analysis without having to edit the *.csproj files directly? (I'm working with a shared code-base and don't want to pollute the project files with SonarQube specific configuration). I've tried and failed to leverage the Analysis Scope 'Source File Inclusions' and 'Source File Exclusions' settings because the source file