I’ve a problem with SonarScanner.MSBuild.exe in machines with Windows 10. The same source and configuration works well in Windows 8.1.
Just when I run “SonarScanner.MSBuild.exe END”, it finishes well but doesn’t publish to sonarqube.
This was answer for the END command.
C:\ProjectName>“C:\Sonar\ES\project-group\ProjectName\SonarScanner.MSBuild.exe” end
SonarScanner for MSBuild 4.3.1
Using the .NET Framework version of the Scanner for MSBuild
Default properties file was found at C:\Sonar\ES\project-group\ProjectName\SonarQube.Analysis.xml
Loading analysis properties from C:\Sonar\ES\project-group\ProjectName\SonarQube.Analysis.xml
Post-processing started.
SONAR_SCANNER_OPTS is not configured. Setting it to the default value of -Xmx1024m
Calling the SonarQube Scanner…
The SonarQube Scanner has finished
10:33:33.225 Creating a summary markdown file…
10:33:33.23 Analysis results: https://mycompany/sonar/dashboard/index/vbnet-project
10:33:33.231 Post-processing succeeded.
I am quite surprised by the length of the end step log. There should be more information.
This seems quite likely to be a machine configuration issue. Have you checked that all dependencies (java, .net…) are installed (check this document)?
Hi Amaury, I think is a environment problem too. But I don’t know what’s happening, the SonarScanner.MSBuild.exe doesn’t show any clue. I’ve attached the SonarScanner.MSBuild.exe end with verbose: sonar-end.txt (20.9 KB)
java version “1.8.0_181”
Java™ SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot™ 64-Bit Server VM (build 25.181-b13, mixed mode)
Could you provide the log of the begin step too (with /d:sonar.verbose=true )? Also could you let me know the version of your SonarQube? The version of SonarVB and also the version of SonarC#?
You passed /d:sonar-verbose=true instead of /d:sonar.verbose=true to the begin step (dash instead of dot). Could you re-run with the correct syntax and upload again the logs?
The logs mention SonarVB 6.5.0.3766 but the latest released version is 5.1, are you using the official plugins? Also I see that you are using a quite old version of SonarC#, is there a good reason not to update?
Can you create a small console application and put a // TODO: inside. Then run the scanner begin, build and the scanner end and let me know if you have something on your SonarQube instance.
I am sorry I didn’t noticed this before but you said you are on SonarQube 5.6.6 which is no longer supported (current LTS is 6.7.*). It’s always recommended to be at least on LTS version.
Could you upgrade your instance and give it a new try?
I tested in other server with sonar version 6.7.4.38452.
It didn’t work either. Same thing, works running the same sources and configurations in a Windows Server 2018 R2 x64, but in several machines with Windows 10 it don’t work.