- ALM used - GitHub
- CI system used - Github Actions
- Scanner command used when applicable - sonarqube-verify
- Languages of the repository - Typescript
- Error observed
After running several steps in CI (lint, build, test), we trigger the sonar scanner to analyse the project.
For this project, test coverage is low and not really needed so we created a custom quality gate based on Sonar Way with
Condition Coverage is less than 0.0% for new code.
The problem is that the analysis report this:
... Protocol = https: Report status : SUCCESS Check the Quality gate ***/api/qualitygates/project_status?projectKey=broker-service Protocol = https: QUALITY GATE STATUS : ERROR QUALITY GATE HAS FAILED Verification ended in error [new_coverage]: 0.0 LT 80 ...
So it seems to still require the 80% coverage from the Sonar way quality gate.
What is even more mysterious to me, is that the PR decoration indicates
Kudos, SonarCloud Quality Gate passed!
Hopefully this issue is not really one, but i cannot find the proper setup neither a discussion that would lead to a consistent result.
So i would appreciate advice to solve it.