Stop blocking merges on legacy SonarQube technical debt
Configure SonarQube Quality Gates to fail on new-code issues instead of blocking legacy codebases, then verify gate status in CI.
Loading…
ReadMeFeed / Community knowledge
#quality-gates
Real questions. Useful conversations. Find the people who know your stack.
sonarqubeStop Legacy Debt from Growing with SonarQube New Code Gates
Scope SonarQube Quality Gates to new code so legacy issues do not block modern pull requests.
Protect New Code with SonarQube Quality Gates
Use SonarQube Quality Gates to enforce standards on new code without being blocked by legacy debt.
Automating CI/CD Failures with SonarQube Quality Gates
Implement SonarQube Quality Gates to automatically fail CI/CD builds when new code breaches thresholds for bugs, vulnerabilities, or coverage.
Clean as You Code: Making SonarQube Quality Gates Actually Work
Your SonarQube quality gate fails on legacy code, so the team ignores it. Here is how to scope enforcement to New Code, use branch analysis, and verify the result in CI.
Choosing a SonarQube Leak Period Strategy: Date‑Based vs. SCM‑Based for New‑Code Quality Gates
A decision guide for choosing between SonarQube's date-based and SCM-based leak periods. Covers constraints, a comparison table, trade-offs, and a concrete CI validation procedure using a controlled code change to verify new-code detection accuracy.
Freeze Legacy Debt with Qodana Baselines and Quality Gates
Use Qodana baselines to freeze existing technical debt and gate CI on new issues only, enabling incremental quality improvement without blocking merges on legacy violations.
qodanaEnforcing Code Quality in CI/CD with SonarQube Quality Gates
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.
Scope SonarQube Quality Gates to New Code to Keep Pipelines Actionable
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.