Quality Gate Failure After Renaming Projects in Azure DevOps

SonarCloud
1

Description:
I encountered a Quality Gate failure with 0% coverage after renaming projects in my Azure DevOps environment. Here are the details:

  1. ALM Used: Azure DevOps
  2. CI System: Azure DevOps
  3. Languages of the Repository: C#

Issue:
The coverage is reported as zero, which likely caused the Quality Gate failure. Although I didn’t write any new code, I did rename the projects. Consequently, I had to remove and re-add them. Additionally, I fixed all the build files after renaming the projects.

Solution Structure Before Renaming:

  • Solution (abc)
    • ProjectA
    • ProjectB
    • ProjectC

Renamed Solution:

  • Solution (xyz)
    • ProjectX
    • ProjectY
    • ProjectZ

During the renaming process, I ensured that all references were correctly updated. How can I address the coverage issue and achieve a successful Quality Gate status?

2

Hi,

Welcome to the community!

The first step is to check your analysis logs to see what they say about your coverage reports. I’m guessing they’re full of warnings that results are being ignored because they’re for file names analysis doesn’t recognize.

Can you post your log? The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

 
Ann