Mismatch between SonarQube server state and API response after PR reanalysis in CI/CD pipeline

[Colin]

@Santiago_Bosch_River

Between the analyses and the API calls, there is a pipeline pause of around 2 seconds to allow the analysis to settle, and beforehand, an API call is made to check if the token is valid. Afterwards, we perform the GET requests for issues and hotspots.

2 seconds seems like an awfully short time. You can check how long your background tasks typically take to process by checking the background tasks.

You can also add sonar.qualitygate.wait=true as an analysis parameter to not allow the scan process to finish until the background task processing is completed, but this will also fail your pipelines if your Quality Gate has failed.