ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Security & identity · #sonarqube
Diagnostic guide for SonarQube Java analysis that succeeds but shows zero or missing new-code issues.
Configure SonarQube Quality Gates to fail on new-code issues instead of blocking legacy codebases, then verify gate status in CI.
Scope SonarQube Quality Gates to new code so legacy issues do not block modern pull requests.
Use SonarQube Quality Gates to enforce standards on new code without being blocked by legacy debt.
Choose between IntelliJ’s fast inline inspections and SonarQube’s cross-project quality metrics. This guide outlines constraints, trade-offs, and a validation workflow for Java teams.
Stop technical debt from leaking into your codebase. Learn how to use SonarQube Quality Gates to automate 'stop-the-line' decisions in your CI/CD pipeline.
Implement SonarQube Quality Gates to automatically fail CI/CD builds when new code breaches thresholds for bugs, vulnerabilities, or coverage.
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.
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.
intellij
java