SonarCloud webhook failure to jenkins

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
  • Scanner command used when applicable (private details masked)
  • Languages of the repository
  • Only if the SonarCloud project is public, the URL
    • And if you need help with pull request decoration, then the URL to the PR too
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
  • Steps to reproduce
  • Potential workaround

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

We have added a webhook in SonarQube for a Jenkins job. Most of the time, the webhook is unable to reach out to Jenkins to update the status of SonarQube task as shown in the below screenshot.

When we restart the Jenkins, it can send the status to Jenkins as shown in the below screenshot

image

But subsequent builds in Jenkins are aborted by waiting for the status as shown in the first screenshot. When we checked the status of webhook in SonarQube, we saw the status as shown in the below screenshot

As we have analyzed the issue with various documentations and knowledge base articles, The memory and cpu resources of Jenkins pod need to be increased so we have done that as well. But it is not resolving the issue. The webhook URL is resolving as shown in the screenshot below

Hi,

What sits on your network in front of your Jenkins instance? Is there a load balancer?

 
Thx,
Ann

Hi Ann,

Yes. There is a NLB and nginx ingress controller sits in front of jenkins instance. Jenkins running as a container in EKS (elastic kubernetes service)

Thanks,

Mani

Hi Mani,

Thanks for the details. I’ve flagged this for the team.

 
Ann