Intermittent connectivity issue with SonarQube-Jenkins

[anon67236913]

Hi,

this is your second jenkins related post.
Did you configure a custom log recorder in Jenkins as proposed here ?

SonarQube is able to send back QG status without webhook

Hi, did you check the computing times of the background task for the jobs in question = no webhook added ? the scanner workflow After analysis is finished, the report archive is uploaded to Sonarqube server, you should see the analysis id on the administration / background tasks page. waitForQualityGate() does an initial call to Sonarqube server to see if the background task is already done - if yes, there’s no need to wait for webhook. You will see such entry in the Jenkins console log, …

To see what’s going on in Jenkins you should create a custom Jenkins Sonarqube logger
(/manage/log/new) with configuration logger hudson.plugins.sonar and org.sonarsource .

And do you use the Sonarqube scan in parallel step ?
Because we had intermittent timeouts when trying to speed up our npm builds via running 1-n Sonarqube scans in parallel.

see

Sonarqube Scanner for Jenkins, analysis in parallel ? [SONARJNKNS-316]

Hi, we want to speed up several parts of our Jenkins pipelines, including the Sonarqube analysis. AFAIK the analysis in parallel is still not officially supported, Sonarqube docs has If you want to run multiple analysis in the same pipeline and use waitForQualityGate you have to do everything in order Some teams nevertheless use the Sonarqube analysis in parallel, the duration of the analysis is reduced from 8-9 mins to 2-3 mins. The parallel scans are running fine most of the time, bu…

@Colin the Jira ticket has moved to https://sonarsource.atlassian.net/jira/software/c/projects/SONARJNKNS/issues/SONARJNKNS-316 and is still in backlog. Has it been simply forgotten or are there new tickets for this problem ?

Gilbert