Qodana Baseline: How to Suppress Known Issues and Keep CI Focused on New Bugs

When Qodana Floods Your CI With Accepted Issues

Running qodana run on a mature codebase often surfaces dozens of issues that have already been reviewed and accepted. These “known” problems clutter the report, mask new bugs, and can cause false‑positive quality gate failures. The baseline feature lets you hide exactly those accepted issues and surface only the newly introduced ones.

Recognizable Condition

After a Qodana run you see a large number of problems, but the New problems tab is empty or almost empty. The pipeline still fails because the total issue count exceeds the quality gate threshold.

Cause & Diagnostic Table

Symptom	Possible Cause	Diagnostic Check
Baseline file missing	Baseline never generated or deleted	Check for .qodana/.baseline in the repo root
Baseline stale	Code changes made after baseline generation	Compare issue counts: qodana --show-baseline vs. current run
Baseline suppresses new issues	Baseline entries match new problems by ID or rule	Inspect baseline file for matching issueId entries
Baseline file too large	Absolute paths or duplicated entries	Check file size and path formatting

Ordered Checks

1. Verify Baseline File Presence
   Run ls .qodana/.baseline from the project root. If it does not exist, you are in the “baseline missing” scenario.

2. List Suppressed Issues
   Execute qodana --show-baseline to see which issues the baseline currently suppresses. Note the count.

3. Run a Fresh Analysis
   Run qodana run without any baseline flag. Compare the total issue count to the baseline count. If the difference equals the baseline count, the baseline is effectively hiding known issues.

4. Validate Baseline Paths
   Open .qodana/.baseline and inspect the path fields. They should be relative; if you see absolute paths like /home/user/project/src, the file will break on other CI runners.

5. Check File Size
   If .qodana/.baseline is >10 MB, suspect misconfiguration or duplicate entries.

Fixes Tied to Findings

• Baseline Missing
  Generate a new baseline and commit it:

  qodana --baseline generate
  git add .qodana/.baseline
  git commit -m "Add Qodana baseline"
  

  Ensure you run the command from the same machine that will run CI to avoid absolute paths.
• Baseline Stale
  After resolving accepted issues, regenerate:

  qodana --baseline generate
  

  Commit the updated file.
• Baseline Suppresses New Issues
  Open the baseline file, locate the issueId of the new problem, and delete that entry. Re‑run Qodana to confirm the problem now appears under New problems.
• Large Baseline File
  Run qodana --baseline generate --baseline-relative-paths to force relative paths, then re‑commit. Remove any duplicate entries manually if size remains high.

Practical Verification

After applying the baseline, run Qodana locally with --baseline apply and inspect the report. The Baseline applied badge should appear in the web UI, and the New problems list should contain only the issues you introduced in the last commit.

Escalation Criteria

• Baseline regeneration fails repeatedly (non‑zero exit code).
• Baseline file exceeds 10 MB after applying --baseline-relative-paths.
• New issues keep appearing in the baseline despite manual removal.
• CI pipeline continues to fail due to quality gate even after baseline application.

At this point contact your CI platform support or the Qodana team for deeper diagnostics.

Key Takeaway

Use Qodana’s baseline to filter out known, accepted issues. Generate the baseline once, keep it in version control, and regenerate it only after you’ve resolved or accepted new problems. This keeps your CI alerts focused on genuinely new bugs and prevents quality gates from being hit by stale code smells.