Coverity Scan是否支持多Git分支扫描及分支独立结果展示？

Can I get branch-independent results in a single registered Coverity project? #

Short answer: No, not with the free Coverity Scan for Open Source Projects. The default behavior of Coverity Scan ties all analysis results to a single project baseline. When you upload results from different branches, it compares the new scan against the last uploaded result (regardless of which branch it came from), which leads to those misleading "new defect" / "defect removed" counts because it’s treating branch-specific code differences as actual defect changes.

Paid Coverity versions do offer streams—a feature that lets you isolate analysis results for different branches, tags, or variants under a single project. But this isn’t available in the free open-source tier.

What’s the best workaround for open-source projects? #

Your most reliable option is to create three separate Coverity Scan projects, one for each branch (v9_11, v9_14, master). Here’s how to make this work smoothly:

• When registering each new project, use the same Git repository URL, but give each project a distinct name (e.g., "MyProject-v9_11", "MyProject-v9_14", "MyProject-master") to keep them organized.
• For each branch, configure your scan script to:
  1. Check out the target branch and ensure the working directory is clean (no uncommitted changes).
  2. Run cov-build as usual to generate the analysis artifacts.
  3. Upload the results using the unique project token for that branch’s Coverity project (you can find this token in each project’s settings page).

This way, each branch has its own independent baseline, so defect counts will accurately reflect changes within that branch—no more false positives from cross-branch comparisons.

Quick tips to avoid confusion #

• Keep your scan scripts branch-specific: Store each branch’s project token in a separate environment variable or config file to prevent uploading to the wrong project.
• If you’re using CI/CD (like GitHub Actions, GitLab CI), set up separate workflows for each branch that trigger the scan and upload to the corresponding Coverity project.

内容的提问来源于stack exchange，提问作者newman