# SonarQube Code Analysis Expected — Waiting for status to be reported

**URL:** <https://community.sonarsource.com/t/sonarqube-code-analysis-expected-waiting-for-status-to-be-reported/91856>\
**Category:** SonarQube Server / Community Build\
**Tags:** coverage\
**Created:** [June 1, 2023, 9:51am UTC](https://community.sonarsource.com/t/sonarqube-code-analysis-expected-waiting-for-status-to-be-reported/91856 "2023-06-01T09:51:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [June 1, 2023, 12:43pm UTC](https://community.sonarsource.com/t/sonarqube-code-analysis-expected-waiting-for-status-to-be-reported/91856/2 "2023-06-01T12:43:21Z")

</div>

Hey there.

Take a look at this thread here:

> [@SonarQube 10.0 not reporting quality gate status and PR decoration in Azure DevOps](https://community.sonarsource.com/t/sonarqube-10-0-not-reporting-quality-gate-status-and-pr-decoration-in-azure-devops/89183/10):
>
> 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](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarqube)) 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…

---

_[View the full topic](https://community.sonarsource.com/t/sonarqube-code-analysis-expected-waiting-for-status-to-be-reported/91856)._