Azure DevOps Pipeline giving Timeout Error

SonarQube Server / Community Build
1

Hi Team,

We have 60 Azure devops classic pipelines and doing SonarQube Analysis at same time let’s say triggering the builds at 6AM and out of 60 pipelines, 40 pipelines are giving timeout exceeded errors.

SonarQube- Community Edition we are using.
Version: * Community Edition * v10.6 (92116)

We have added pipelines delays as well but still getting below error. Please help.

03:07:14.422 INFO: :----|----------:|--------:

03:07:29.648 INFO: ------------------------------------------------------------------------

03:07:29.648 INFO: EXECUTION FAILURE

03:07:29.648 INFO: ------------------------------------------------------------------------

03:07:29.648 INFO: Total time: 17:43.973s

03:07:29.695 INFO: Final Memory: 23M/272M

##[error]03:07:29.695 ERROR: Error during SonarScanner execution

03:07:29.695 ERROR: Error during SonarScanner execution

03:07:29.695 INFO: ------------------------------------------------------------------------

##[error]Quality Gate check timeout exceeded - View details on SonarQube

Quality Gate check timeout exceeded - View details on SonarQube

03:07:29.695 DEBUG: Cleanup org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda/0x00000168f2334f38@6dd82486 during JVM shutdown

Process returned exit code 1

##[error]The SonarScanner did not complete successfully

The SonarScanner did not complete successfully

##[error]03:07:30.775 Post-processing failed. Exit code: 1

03:07:30.775 Post-processing failed. Exit code: 1

##[warning]Can’t find loc string for key: LIB_ProcessExitCode

##[warning]Error while executing SonarQube:Analyze task: LIB_ProcessExitCode C:\VD808211_work_tasks\SonarQubePrepare_15b84ca1-b62f-4a2a-a403-89b77a063157\6.3.4\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe 1

##[error]LIB_ProcessExitCode C:\VD808211_work_tasks\SonarQubePrepare_15b84ca1-b62f-4a2a-a403-89b77a063157\6.3.4\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe 1

Finishing: Run Code Analysis

2

Hey there.

It looks like you’ve added sonar.qualitygate.wait=true to all your pipelies, which means that the analysis won’t finish until the server-side background task has finished processing. If you’re triggering all your builds at once, that’s going to lead to some delays (since they process 1 at a time).

  • You can extend the timeout, using sonar.qualitygate.timeout
  • You can decide not to check for the Quality Gate status at the end of analysis (remove sonar.qualitygate.wait)
  • You may want to consider if a nightly analysis is really relevant, as opposed to scanning after merges to your main branch. This would probably reduce the load at any one given time on your SonarQube server.