The JSON snippet from the first post in this thread is about
“metricKey”:“code_smells”
but Code Smells don’t appear in your screenshot. At a guess, you have multiple Quality Gates configured, and a different QG than you think is being applied to your project.
Your log shows that the DFW CICD Quality Way profile is being used (for Java). The selection of a profile has nothing to do with the selection of the quality gate, similarly named or not. To know for certain which quality gate was applied on your last analysis, look at the bottom-right of the project homepage:
The project homepage indicates that the Quality Gate has passed for the master branch;
however, the feature branch in question indicates that there is one minor issue.
The JSON snippet is retrieved by calling the project_status API by passing in the analysisId.
The analysisId is retrieved from the maven command that is used to check if the project passed the quality gate.
Unfortunately, I can only include one screenshot per post;
please take a look at the image below regarding the screenshots of the quality gate and how the JSON snippet was populated:
Thanks for the screenshots. Now I understand what’s going on. There is currently a hard-coded Quality Gate(QG) for PRs and Short-Lived Branches (SLBs): no open issues. Your SLB is failing the QG because it fails that test. You can Confirm the issue if you’d like the SLB to pass the QG with that single issue.
SonarQube 7.7 will include real QGs for PRs and SLBs.