Currently have: Jenkins (version 2.289.2) SonarQube (Community Edition Version 8.5.1 (build 38104)) Running in GCP Kubernetes. I’m currently integrating SonarQube in Jenkins and after having configured SonarQube server and SonarQube scanner in Jenkins. To test if everything is ok I put up a sim…

I already did it, it turns out that on the url field I needed to put the “ http://sonar-service:9000/sonar ” to this to work. I was putting the actual URL that people can acess sonar! Now I’m getting a: Bad Message 431 reason: Request Header Fields Too Large Another error to find and solve …

Jenkins & Sonar: fails after "Get boostrap completed"

SonarQube Server / Community Build

system (system) Closed August 18, 2021, 2:26pm 7

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

Topic		Replies	Views
There is a problem: Fail to parse entry in bootstrap index SonarQube Server / Community Build sonarqube , jenkins	2	4434	August 14, 2019
Jenkins: org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarQube SonarQube Server / Community Build	4	3208	July 17, 2019
Jenkins build fails to run the SonarQube scanner SonarQube Server / Community Build sonarqube , jenkins	4	2687	October 21, 2020
Unable to execute SonarQube scanner SonarQube Server / Community Build	1	7019	April 27, 2020
Issue regarding sonarqube jenkins integration SonarQube Server / Community Build sonarqube , jenkins	18	12686	July 26, 2019

Jenkins & Sonar: fails after "Get boostrap completed"

Related topics