'Pipelines are taking time to open after Sonar upgrade

We recently migrated our Sonar from on prem to EKS and upgraded to Enterprise from developer. ON prem version - Developer Edition- Version 7.9.1 (build 27448) EKS/Upgraded version - Enterprise Edition -Version 8.9.7 (build 52159)

After this migration we observed our Jenkins pipeline are taking time to open after if the Sonar scan is executed from the pipeline .

Jenkins version - Jenkins ver. 2.164.2 Jenkins Sonar Scanner plugin version - 2.8.1

Did any had the similar issue, If so can you help me solving this .

jenkinssonarqubejenkins-pipelinejenkins-pluginssonarqube-scan


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions

Jenkins Content Security Policy

setUp method: Failed to connect to binary FirefoxBinary(/usr/bin/firefox) on port 7055; process output follows:

SonarQube 3.7 with maven and Jenkins - Maven session does not declare a top level project

How can I pass variables to post-build actions in Jenkins?

How to add a timeout step to Jenkins Pipeline

Jenkins not building docker image, can't find the docker command

compare 2 variables in jelly script

Jenkins Ambiguous Permission

Error - Jenkins detected running multiple instances

How to get child job logs in parent job on child job failure?

create jenkins ssh username with private key credential via rest xml api

How to stop build from executing from the pipeline script?

How to prevent Jenkins SCM polling from triggering a build on branch creation

jenkins builds filtering based on build description

Jenkins shell script returned exit code 1 when the searched string isn't exsist