which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
SQ 7.9.1LTS
what are you trying to achieve
Did the Upgrade from SQ 7.5 to 7.9.1
And hence all builds are having a timeout issue.
what have you tried so far to achieve this
We set up a build variable: SonarQubeAnalysisTimeoutInSeconds that was set to 300 then 600 secs. Even then the build timed out.
Logs of the error report:
2019-08-05T19:28:24.0704393Z Waiting on the SonarQube server to finish processing in order to determine the quality gate status.
2019-08-05T19:28:24.1173166Z SonarQubeAnalysisTimeoutInSeconds is set to 600 and will be used to poll for the SonarQube task completion.
13. 2019-08-05T19:38:24.8439768Z ##[error]The analysis did not complete in the allotted time of 600 seconds. Consider setting the build variable SonarQubeAnalysisTimeoutInSeconds to a higher value.
Can someone please help resolve this issue, as non on the builds across projects are able to publish the reports. What is it, that we are missing for 7.9.1??
2019-08-05T19:28:24.0079453Z ##[debug]received 11-byte response of content type text/plain
2019-08-05T19:28:24.0704393Z Waiting on the SonarQube server to finish processing in order to determine the quality gate status.
2019-08-05T19:28:24.1173166Z SonarQubeAnalysisTimeoutInSeconds is set to 600 and will be used to poll for the SonarQube task completion.
2019-08-05T19:38:24.8439768Z ##[error]The analysis did not complete in the allotted time of 600 seconds. Consider setting the build variable SonarQubeAnalysisTimeoutInSeconds to a higher value.
This looks like the Jenkins log for the individual run/job. I was asking about the Jenkins server log.
If you’re not sure you have webhooks set up, then that’s probably the problem. Theoretically, the Jenkins pipeline submits the analysis report to SonarQube, suspends and waits to be asynchronously notified by SonarQube of the Quality Gate results. That notification comes via webhook.
In that context, this log line from your OP is a little odd (emphasis added):
Since my math says 600 seconds == 10 minutes that means that either no polling is taking place or that the background task processing queue on the SonarQube side is way longer than I would expect.
So…
First you should check out webhooks. If those are actually in place, then take a look at your Jenkins server log to see if you can find evidence that the webhooks are being received, and if they are, then post your pipeline code here (code-formatted, please with ``` on the line before and the line after).