A few days ago our SonarQube administrators removed the BuildBreaker plugin, so I had to get the “recommended approach” using webhooks to work. I had previously tried it and it didn’t work. The pipeline step to wait for the quality gate never returned.
It wasn’t working on Friday, but for some reason over the weekend it simply started working. I don’t know whether some admin changed something or not. I’ll find out more on Tuesday.
However, one thing did occur to me. I had started testing this by setting the webhook url in one project and testing builds for that project.
I have another project that is a copy of that first project, but without a webhook url. What I noticed is that both builds are now getting past the “wait for quality” gate step, even the one that doesn’t have a webhook url.
This leads me to wonder, what is the point of setting the webhook url anyway? I can see the documentation saying what information it sends to Jenkins, but what makes use of this information? The only place I’m aware of that Jenkins looks at SonarQube is in this “wait for quality gate” step, and that appears to be working fine (for some reason) without any webhook url.