I have created a simple quality gate which says that number of new critical and blocker issues should be zero. This quality gate is passing on each PR I raise but is failing on analysis of master branch. It shows at the top the count for both blocker and critical issues are zero and are expected to be zero but it always fails. I am unable to find why this is happening. Logs also do not indicate any reason for the same.
Can you please elaborate on this? From the jira issue, it seems there is not way to specify separate quality gates for PRs and main code. Currently, I am using approach one of applying quality gate on new code only so that works for PR as well.
By the way I was able to solve the issue by deleting the project and recreating it. I think the issue was due that my trial license had expired and I had an analysis which blocked due to expired license. When I reapplied a new license, it was not able to turn the QG status from Red to Green even though no issue exists in the main code. May be a bug.
I am again facing this issue. Regardless of whether I run analysis on a PR or a normal builds, once the quality gate turns RED, it never turns back to Green even when no issues are reported. Initially, it is turning RED randomly without reporting of any issues in the scan. Is this a bug?
I am running SonarQube server 7.3 Developer Edition with a trial license. Can somebody help me with this?