Template for a good new topic, formatted with Markdown : ALM used: Azure DevOps CI system used: Azure DevOps Scanner command used when applicable: Using task SonarCLoud Prepare (Cli Mode) Languages of the repository: Angular Error observed: Apparently on October 1st, our SonarCloud …

Hi @andressantos10 , thanks for the test! About the short living branch coverage: it is based on the new code introduced on that branch. For long living branch this is different: we use the new code definition to deduce what is effectively new code. I think you got zero coverage on the testing short…

@Alexandre_Holzhey , yes! We need firt-analysis for “release-v” branches. However I have doubts if we will be effective. My flow, with details: Concept branch: Branchs develop, master and release-v* are considered long living. Branchs feature-v* and hotfix are considered short living. Step 1: My…

@Alexandre_Holzhey do you have updates about this case? Tks.

Hi @Alexandre_Holzhey , I have the same Problem that Andre. The Sonar has one update?

[image] andressantos10: @Alexandre_Holzhey do you have updates about this case? Tks. Hi @andressantos10 . The Quality Gate can have rules based on 2 conditions: new code and/or overall code. The default one uses new code conditions. When configuring it only with rules based on overall code, i …

Hi @Alexandre_Holzhey , I already used the overall code model in my scenario, the problem is that I have no options. Since I have to define “new code” at the organizational level, any changes I make will not have the expected effect. Ideally, SonarSource would rollback the change or allow me to use…

Hello @andressantos10 , First of all thank you for providing detailed descriptions of your workflow :+1:. If I understood correctly, you are creating release branches (long-living) from your develop branch and do not make any changes to them. Then, they undergo a QA process and are later merged wit…

Hello @Martin_Bednorz , same case that @andressantos10 here. My long living branches correspond to releases have “no computed status” as they are analyzed only once, just when the master branch is tagged. Is there any way to remove “new code” conditions only for long living branches, so they could …

Hello @Martin_Bednorz and @Alexandre_Holzhey , I have the same use case where release branch are used in build pipelines and it is showing as Not computed because of the same reason which is discussed in this topic. Is there any solution for it? Is it possible to always compare first scan with mas…

SonarCloud Gate : Not Computed Status

SonarQube Cloud

Alexandre_Holzhey (Alexandre Lehmann Holzhey) November 5, 2020, 8:08am 24

As mentioned before we updated the new code feature. Are you also missing the quality gate on long living branch analysis? Have you looked the previous messages in this topic and found something that could help?

Topic		Replies	Views
Approach to incrementally improve quality by Quality Gate on PR branches SonarQube Cloud cfamily , coverage , quality-gate	7	359	July 3, 2024
Quality gate pass on some branches by fail on others SonarQube Cloud maven , scanner , gitlab , sonarqube-cloud	5	1329	June 17, 2022
Block Pull request based on Quality gate code coverage on new code SonarQube Server / Community Build coverage , quality-gate , new-code	17	2786	September 6, 2022
Scans of new-style branches no longer fail quality gates SonarQube Server / Community Build sonarqube , scanner	21	2997	August 18, 2023
Existing issues reported in branches. Develop plugin to avoid? SonarQube Server / Community Build sonarqube	7	2596	June 13, 2019

SonarCloud Gate : Not Computed Status

Related topics