Enforcing Build Failures with SonarQube Quality Gates
Learn how to configure SonarQube Quality Gates to automatically fail CI/CD builds when new code violates security or quality thresholds.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to configure SonarQube Quality Gates to automatically fail CI/CD builds when new code violates security or quality thresholds.
Learn how to run IntelliJ IDEA’s full inspection suite in CI/CD with Qodana, configure custom profiles, and generate SARIF reports for automated quality gates.
Decide whether to run Qodana in Docker or install it locally. Compare isolation, speed, and version control, then see a GitHub Actions workflow that pulls the image, runs the scan, and uploads the HTML report.
Learn how to extend Codeac’s static analysis by writing lightweight YAML rules that enforce project‑specific coding standards. From authoring to CI integration, this guide walks you through a concrete example, trade‑offs, and best practices.
Enable Sema's SARIF output to feed static analysis results into GitHub Code Scanning, GitLab SAST, and IDEs. Covers CLI flags, sema.yaml config, a complete GitHub Actions workflow, schema version pitfalls, large-file handling, and a verification checklist.
ESLint --fix can clear formatting noise in seconds, but it won't fix unused variables or logic bugs. Here's a safe workflow and the limits to know.
SonarQube Quality Gates decide whether a pipeline passes. Configure the New Code baseline, poll gate status from CI, and choose which conditions are worth blocking on.
Stop legacy warnings from drowning out new bugs. Learn how to implement and manage Qodana baselines to suppress technical debt while enforcing a zero-new-issue policy in CI.
Learn how to create a Qodana baseline that records existing warnings so your CI only flags newly introduced problems, with a concrete configuration example and notes on maintenance.