We’ve got a slow-moving, but on-going initiative to embed relevant bits of documentation in the UI. You’ve made me realize this is a good candidate, so I’m going to see what I can get added for 7.5. Hopefully by 7.6 we’ll have real quality gates (no promises!) and this becomes moot.
The down side of this particular approach is that it actually generates a significant amount of churn in shops with fully/heavily automated CI/CD systems. The reason I found this post to begin with was because I was trying to resolve issues with Jenkins failing jobs because the build is failing due to the quality gates. So the reality of my situation is that developers push a commit, jenkins kicks off the build pipeline, sonarqube fails the quality gate because someone has an informational issue in the code (that would have been allowed to leak by policy, not manual exception), now a developer has to go into sonar and see what’s up (which they don’t have to do normally because they get the reports linked through IntelliJ and may not actually have access to sonar since there is usually no need), mark the items appropriately, and then trigger a new build so that the quality gate can pass.
I appreciate that there is a work around for the issue. It is unfortunate that it is a manual work around that impedes automation and policy enforcement, and diverts resources from positive business value areas. It just seemed like a significant step backwards for such a wonderful product.
The quality gate flips to passing as soon as you do something with the last Open issue.
If your problem is not the quality gate but the build… well, we’ve said for a long time that breaking the build because of quality issues isn’t the best strategy. We nonetheless added webhook notifications so you can notify external systems of your project’s QG status. In addition, we fire the webhook when manual issue changes flip the QG status.
Thanks. I think.
Just to repeat onemoretime, we recognize this is sub-optimal and plan to get to the point of offering real, user-controlled quality gates on PRs and SLBs. We’ve delivered interim stages of the product because we believe in delivering, rather than waiting until we’ve got a theoretically “feature-complete” version.