Sonar cloud quality gate not triggered in pull request

[hddbl (HD)]

I’m executing the dotnet sonarscanner inside a dockerfile, in the pipeline the analysis is successful, could see the same in sonar cloud dashboard. But the results are not reflected in the azure devOps Pull requests status. Also tried setting quality gate wait though no help

dotnet sonarscanner begin \
  /k:${PROJECT_KEY} \
  /o:${OGRANIZAION_KEY} \
  /d:sonar.host.url=${HOST_URL} \
  /d:sonar.token=$(cat /TOKEN) \
  /d:sonar.pullrequest.key=someid \
  /d:sonar.pullrequest.base=master \
  /d:sonar.pullrequest.branch=somebranchname \
  /d:sonar.qualitygate.wait=true

[Colin]

Hey there.

Take a look at this thread:

Publishing code analysis results to AzureDevops from docker

Hey @Plevi1337 Thanks for the details. My understanding is that when the project is bound there should be data that’s always available to SonarCloud when decorating PRs. That data doesn’t seem to be there on the PR you shared with me. This is data that is set also by the Extension for Azure DevOps (but only meant to be used when a project isn’t bound). That’s these analysis parameters and corresponding build variables: sonar.pullrequest.vsts.instanceUrl - System.TeamFoundationCollectionUri s…

For what it’s worth – we recognize there’s a bug here that is in the backlog to fix. In the meantime, you can populate these analysis parameters.

[hddbl (HD)]

Hi Colin,

Thanks for the earlier suggestion. I applied the suggested changes and I am able to see the results in pipeline but not in the azure devOps pull request dashboard. Am I missing any configuration ?
We do we have other dotnet projects (not docker build), there the status is updated without any issues.

[Colin]

Are you sure that the values you’re passing (DEVOPS_URL, VSTS_PROJECTNAME_ SONAR_PROJECT_KEY) match exactly the values that the other post references?

sonar.pullrequest.vsts.instanceUrl - System.TeamFoundationCollectionUri
sonar.pullrequest.vsts.project - System.TeamProject
sonar.pullrequest.vsts.repository - Build.Repository.Name

[hddbl (HD)]

Hey Colin,

I made sure the values are correct.
However in other projects, we use following pipeline tasks and not docker build

SonarCloudPrepare@1
SonarCloudAnalyze@1
SonarCloudPublish@1

[Colin]

In those cases, you won’t need to use these analysis parameters at all, as the values get automatically populated.

@hddbl

However in other projects, we use following pipeline tasks and not docker build

Are you saying that the PR decoration also doesn’t work in these cases?