ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Security & identity · #sonarqube
Configure SonarScanner to wait for the Quality Gate and fail your pipeline when new-code issues violate the gate, then verify with a deliberate violation.
Learn how to configure SonarQube 'New Code' definitions to implement effective Quality Gates that focus on recent changes without being overwhelmed by legacy technical debt.
Use SonarQube Quality Gates to enforce code quality thresholds in CI/CD. Learn how to set up gates, integrate them into GitHub Actions, understand trade‑offs, and verify results locally.
Discover how SonarQube’s Compute Engine separates scanner output from database updates, and learn how to size, configure, and monitor it to keep CI pipelines responsive.
Enforcing SonarQube Quality Gates on Overall Code blocks builds on legacy debt. Configure conditions against New Code metrics and use sonar.qualitygate.wait=true so CI fails only on recent changes.
Learn how SonarQube Quality Gates enforce pass/fail thresholds, how to configure conditions and make your CI pipeline wait for the result, plus common pitfalls.
Learn how to configure SonarQube's Leak Period so that quality gates only flag issues introduced after a reference point, reducing noise from legacy debt.
Stop relying on default SonarQube settings. Learn how to build custom Java quality profiles and strict quality gates to catch critical bugs before they hit production.
Introducing SonarQube to a legacy Java codebase without blocking delivery: scope Quality Gate conditions to New Code, wire JaCoCo coverage, and verify the gate actually blocks CI.
java