SonarQube Azure DevOps quality gates not working since 10.x

[rafal.prokopowicz.sp (rafal.prokopowicz)]

Hello,

We’ve recently upgraded our sonar instance to 10.2.1 from 9.9.2 LTS and noticed that Quality Gates in Azure DevOps stopped working correctly they are constantly hanging on Waiting.

We are using:
Sonarqube Developer Edition Version 10.2.1 (build 78527) (Docker image on AKS)
Azure DevOps (Latest)
SonarQube extension version 5.15.0 (Latest)

We have configured Projects in sonarqube to integrate with Azure DevOps (DevOps Platform Integration) and have Valid Azure DevOps configuration on administration panel

Is there anything else we need to configure to make it work?

[Colin]

Hey there.

Check out this post.

SonarQube 10.0 not reporting quality gate status and PR decoration in Azure DevOps

Hey all. In SonarQube v10.0, we removed some deprecated analysis parameters which, among other things, automatically fed the ALM Integration information when in an Azure Pipelines context (using the Extension for Azure Devops) This was old behavior, kept for compatibility reasons, and we’ve encouraged users to set the ALM integration configuration in their Project Settings for some time now. Right now, there’s no method of automatically populating this data from information available to the s…

[rafal.prokopowicz.sp (rafal.prokopowicz)]

Hi,

Thank you for the quick reply.
As I mentioned we already have setup ALM Integration on project level and in administration panel but it still doesn’t work. Did we need to configure it anywhere else beside this two places for quality gates to work in PRs?

.

[Colin]

No, that’s all the configuration that should be required.

Do you see the pull request itself analyzed in SonarQube (putting the decoration aside)? Any warnings on the project dashboard?

[rafal.prokopowicz.sp (rafal.prokopowicz)]

The build that the PR triggered passed without errors and i can see the results in SonarQube

The only warning we are getting is about login parameter, doesn’t seem related to our problem.

[Colin]

Okay — that’s unfortunate.

My next suggestion would be to check the Compute Engine logs (the ce.log file of your /logs/ directory) after submitting an analysis of this pull request. Maybe it’s swallowing some errors instead of making them visible on the UI.

[rafal.prokopowicz.sp (rafal.prokopowicz)]

We’ve done some digging and found out the reason for our problem, seems like old version of azure devops tasks are not compatible with current version of SonarQube.
After changing them to latest ones PR’s started working correctly.

Thank you for your hints!