Jenkins error while running sonarqube

Hi,

we are facing below Jenkins error below while running an analysis for a 2 GB repo.

**15:42:29** [INFO] 10:12:15.162 User cache: /home/ec2-user/.sonar/cache 
**15:42:29** [DEBUG] 10:12:15.162 Create : /home/ec2-user/.sonar/cache/_tmp 
**15:42:29** [DEBUG] 10:12:15.162 Extract sonar-scanner-api-batch in temp... 
**15:42:29** [DEBUG] 10:12:15.163 Get bootstrap index... 
**15:42:29** [DEBUG] 10:12:15.163 Download: https://sonarqube.aws.fico.com/batch_bootstrap/index 
**15:42:29** [ERROR] 10:12:15.250 SonarQube server [[https://sonarqube.aws.fico.com](https://sonarqube.aws.fico.com/)] can not be reached

followed by the below errors ,

[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project fire: Unable to execute SonarQube: Fail to download libraries from server: No enum constant org.sonarsource.scanner.api.internal.shaded.okhttp.CipherSuite.TLS_AES_128_GCM_SHA256 -> [Help 1]

 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project fire: Unable to execute SonarQube

if we use the job to analyse a sample new repo for testing, it works fine without any issues.

when checked in online, few suggested checking the scanner version and maven versions but that also didn’t help.

Hi,

The error is pretty clear:

Either this is a misconfiguration of your SonarQube URL, or there’s something going on on the network.

 
HTH,
Ann

This was not an issue with the network but with the incompatible maven versions in dependency POM’s

3.2 is quite old, try with the latest 3.10 and use Java 17 for the scan.
i recommend to always use the latest version of the sonar-maven plugin, see

1 Like