Time out when fetching analysis config settings in Jenkins build using SonarScanner for MSBuild

Hi all,

we have set up SonarQube scanner for MSBuild 4.7.1 to be installed automatically in Jenkins v2.222.1.

The issue we are facing is that we are getting a timeout when fetching analysis config settings like you can see below:

Running as SYSTEM
Building on master in workspace C:\Synxis\ProjectX_Trunk_CI\SHS\EnterpriseServices\Services
Injecting SonarQube environment variables using the configuration: Global Sonar
[Services] $ C:\sonar-runner3.2\SonarScanner.MSBuild.exe begin /k:PROFILES /n:PROFILES /v:1.0 /d:sonar.host.url=https://sonar.sabre.com/ /d:sonar.login=XYZ /d:sonar.ws.timeout=60 /d:sonar.modules=SHS.Services.ProfileManager,SHS.Services.TravelerDA /d:SHS.Services.ProfileManager.sonar.projectBaseDir=Managers/SHS.Services.ProfileManager /d:SHS.Services.ProfileManager.sonar.cs.fxcop.assembly=Managers/SHS.Services.ProfileManager/bin/Release/SHS.Services.ProfileManager.dll /d:SHS.Services.TravelerDA.sonar.projectBaseDir=ResourceAccess/SHS.Services.TravelerDA /d:SHS.Services.TravelerDA.sonar.cs.fxcop.assembly=ResourceAccess/SHS.Services.TravelerDA/bin/Release/SHS.Services.TravelerDA.dll /d:sonar.exclusions=**/v2/* /d:sonar.sourceEncoding=UTF-8 /d:sonar.dotnet.excludeGeneratedCode=true /d:sonar.dotnet.key.generation.strategy=safe
SonarScanner for MSBuild 4.7.1
Using the .NET Framework version of the Scanner for MSBuild
Pre-processing started.
Preparing working directories...
10:27:37.082  Updating build integration targets...
10:27:37.103  Fetching analysis configuration settings...
10:29:17.169  Failed to request and parse 'https://sonar.sabre.com/api/server/version': The operation has timed out

In the logs from jenkins this is what we see (from a previous run, so the timestamps don’t match here):

$JENKINS_IP - - [10/09/2020:03:00:08 +0000] "GET /api/server/version HTTP/1.1" 500 - "-" "SonarQubeRunner/2.4"

Seems like we are getting a 500 back. But when opening the URL https://sonar.sabre.com/api/server/version on a browser from the machine on which Jenkins runs, we are getting a valid response back: “7.9.2.30863”

Does anyone know what could be the issue here?

Thanks in advance
Uwe

The issue was solved by one of our jenkins engineers. The reason was that the build user was associated with wrong internet options / proxy settings. After fixing that (don’t ask me how), fetching the analysis configuration step does not timeout anymore.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.