11

SonarQube is giving me below error when i integrate the xamarin app with jenkins on windows sever

SonarQube Scanner for MSBuild 3.0
Default properties file was found at C:\SonarQube\bin\SonarQube.Analysis.xml
Loading analysis properties from C:\SonarQube\bin\SonarQube.Analysis.xml
Post-processing started.
13:49:43.952  SonarQube analysis could not be completed because the analysis configuration file could not be found: C:\Users\Administrator\.jenkins\workspace\Xamarin-ProjectTemplate\.sonarqube\conf\SonarQubeAnalysisConfig.xml.
13:49:43.952  Post-processing failed. Exit code: 1

I have followed the below guide https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+MSBuild

SonarQube.Scanner.MSBuild.exe begin /k:"org.sonarqube:sonarqube-scanner-msbuild" /n:"Project Name" /v:"1.0"
MSBuild.exe /t:Rebuild
SonarQube.Scanner.MSBuild.exe end

Please help me to resolve this issue

vinay
  • 1,276
  • 3
  • 20
  • 34
  • I had the same error...in order to make it work, instead of `MSBuild.exe /t:Rebuild`, you just need to use `MSBuild.exe` – Hackerman Dec 06 '17 at 12:13
  • @Hackerman, maybe you are right, but there are much more reasons for the same error e ("SonarQube analysis could not be completed..."). – Gerard Jaryczewski Sep 16 '22 at 15:00

5 Answers5

10

The errors reported at the end of a SonarQube report are sometimes less helpful than the errors when you begin.

Eg when I got this error, scrolling to the top of the log showed that I wasn't correctly setting the sonar.projectKey value, but this message the OP shared is still what showed up at the end.

kayleeFrye_onDeck
  • 6,648
  • 5
  • 69
  • 80
  • 2
    this helped me. I found this error near the top: "Invalid project key. Allowed characters are alphanumeric, '-', '_', '.' and ':', with at least one non-digit." – sitting-duck Sep 11 '21 at 22:39
2

I had the same problem. You need find correct MSBuild.exe.

I have several in c:\Windows\Microsoft.NET\Framework64\... and also in c:\Program Files (x86) For my project in Visual Studio 2017 with .NETFramework,Version=v4.6.1 the correct MSBuild.exe is:

"c:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\amd64\MSBuild.exe"  /t:Rebuild

For the Enterpsie version is should be:

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild" /t:Rebuild
mihi
  • 29
  • 2
  • The error message "SonarQube analysis could not be completed..." is a kind of summary, unfortunately, a misleading summary. The REAL reason is usually at the beginning of the log. Your answer is too specific to be applied in this case. – Gerard Jaryczewski Sep 16 '22 at 14:52
0

I got the same error and was able to fix it by excluding "/t:Rebuild" from second step. Also used the VS2017 MSBuild.exe

These are the 3 commands I ran in Windows Command Prompt (CMD):

1>> SonarScanner.MSBuild.exe begin /k:"MyProjectName"

2>> "C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/MSBuild/15.0/Bin/MSBuild.exe" "MySolution.sln" 

3>> SonarScanner.MSBuild.exe end
Natasha Voloshyna
  • 667
  • 5
  • 6
  • 1
    This is not a good answer, @Natasha Voloshyna, if it helped you that was rather accidental, it's so called "false positive". The error message "SonarQube analysis could not be completed..." is a kind of summary, unfortunately, a misleading summary. The REAL reason is usually at the beginning of the log. – Gerard Jaryczewski Sep 16 '22 at 14:48
0

Update I confront this error also , my solution was easy I just build the project in the visual studio then its succeeded.

firatt_
  • 136
  • 2
  • 10
-1

I had this problem because I used a bad project key (it had a }) inside. I removed the }and the problem was gone.

Arnaud Weil
  • 2,324
  • 20
  • 19
  • Possible answers of that kind can be plenty. The error message "SonarQube analysis could not be completed..." is a kind of summary, unfortunately, a misleading summary. The REAL reason is usually at the beginning of the log. Your answer is too specific to be applied in this case. – Gerard Jaryczewski Sep 16 '22 at 14:51