Copy review statuses from one product to another

[jimis]

Hello, I have setup 2 products for the same software:

1. prod-nighty: Building the tip of the main branch every night and storing it as a new run. This is where developers interact and mark the findings as confirmed, intentional etc. There are many hundreds of runs in this product.
2. prod-releases: Here is only one run per release. Few runs in total, so it's much easier to present and browse.

Can I copy the review statuses from prod-nightly to prod-releases? AFAICT the report hashes don't change for the same issue in the two products.

[cookesan]

Yes. Use CodeChecker cmd export on the source product/run and CodeChecker cmd import on the target product URL.

The relevant behavior is that products are separate result databases, so Web UI review state is not shared across products. The CLI export/import path is meant for this kind of transfer: it exports comments and review statuses, and the import side restores them by report hash. The functional tests also exercise changing a review status, exporting it, and importing it back.

Example shape:

CodeChecker cmd export -n <nightly-run-name> --url http://host/prod-nightly -o reviews.json
CodeChecker cmd import -i reviews.json --url http://host/prod-releases

I would test this on one release run first and make sure the target run already exists and the hashes really match. For long-term false-positive handling, in-code suppressions are still more robust because Web UI state remains database/product state.

[jimis]

Thank you! You might want to edit the export command above. It doesn't accept -o argument, instead you have to redirect stdout >reviews.json.

In my case I didn't try specifying the run name since I want to copy data from all runs.
But it's weird that one can specify the run: an issue is not bound to a specific run. So if one leaves a comment/changes status of an issue, these shouldn't be bound to a specific run either.