Using SonarQube's New-Code Quality Gate to Enforce Clean as You Code
Learn how to configure SonarQube's Quality Gate to evaluate only New Code, enabling the Clean as You Code strategy in a typical CI pipeline with Maven and GitHub Actions.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to configure SonarQube's Quality Gate to evaluate only New Code, enabling the Clean as You Code strategy in a typical CI pipeline with Maven and GitHub Actions.
Learn how to configure SonarQube Quality Gates to automatically fail CI/CD builds when new code violates security or quality thresholds.
Learn how to set up, tweak, and enforce SonarQube Quality Gates in your CI pipeline. See a step‑by‑step example, trade‑offs, and how to verify gate status via UI and API.
Learn how to decide between SonarQube’s Leak Period and Overall Quality Gates, see a side‑by‑side comparison, and follow a concrete setup and validation example.
Learn how to configure SonarQube’s Leak Period (New Code) so your quality gate only counts issues introduced after a chosen baseline, reducing noise from historic debt.
Assuming a recent JetBrains JVM linter image, the goal is to use its resource-leak inspections for unclosed Closeable values as a CI guard, so a leak-prone pattern cannot quietly return after a fix. Static analysis inspects source, not runtime behavior, so it complements rather than replaces profiler or heap-dump evidence. Two constraints shape the setup: St
In high-throughput CI environments, the SonarQube Quality Gate evaluation process can introduce significant latency. When multiple projects trigger analysis simultaneously, the default worker pool size may limit the number of concurrent evaluations, causing subsequent analysis tasks to queue. This behavior creates a trade-off between maintaining system stabi