We are using EKS on AWS with :
- Cloudbees Jenkins (latest version)
- SonarQube Scanner for Jenkins (version 2.3)
- SonarQube Enterprise (version 8.6) (using the docker image)
With Cloudbees, we have multiple Jenkins (provided by Cloudbees, aka. masters) assigned to different teams, so we need to add a webhook for each one.
We have made the analysis with Jenkins and it works fine.
But when calling the waitForQualityGate() function, it succeeds in getting the first response, then a listener is added for webhooks and finally the webhook is never reaching Jenkins.
On SonarQube’s side, the webhook is responding " Response: Server Unreachable " most of the time. But with some webhooks it works, in a unpredictable way…
On Kubernetes’ side, we tried to run a wget command on the webhook url, and it works, meaning it is not a network issue.
On Cloudbees’ side, each Jenkins master has a hibernated feature which puts them to sleep. Whenever a command is reaching a hibernated Jenkins, it goes out of sleep and then the command is executed.
We have found that if we restart our SonarQube pods, all webhooks are working well on the beginning. The issue might be because of a loss of connection with a webhook which results in a dysfunction for all webhooks.