Where Does Qodana Store Config and Baselines?
Qodana reads qodana.yaml for inspection profile and run config in each repo, with baselines and SARIF reports beside it, plus IDE inspections shared from JetBrains profiles.
Last updated
Qodana configures per repository through qodana.yaml holding profile names, run scopes, and reporting options. Baselines live beside it marking known debt excluded from fresh reports. SARIF outputs feed pull request checks.
IDE inspections share definitions with Qodana profiles, so tuning locally previews server results. Export profiles from the IDE and commit them for the whole team. Versioned configs keep pipeline behavior reproducible across branches.
Where Qodana stores this, by platform
qodana.yaml
Pipeline inspection config per repo with profile references. Baselines and SARIF beside it. IDE exports feed the same profiles.
qodana.yaml
Same repo relative config on Mac runners. Profile XMLs commit beside YAML. No local state needed.
qodana.yaml
Windows runners read the identical repo file. IDEA inspections export compatible profiles. Secrets stay in CI variables.
Frequently asked questions
How do I add Qodana to a repo?
Add qodana.yaml at root naming the inspection profile and include paths, then trigger on push. Baselines in the repo silence legacy warnings for clean diffs. SARIF uploads feed GitHub code scanning.
How do Qodana and IDE inspections relate?
Export the profile from IDE inspections settings and reference it by name in qodana.yaml. Both consume the same inspection definitions. Keep the exported XML versioned beside the YAML.
Notice an outdated path? Let us know.