Our quality metrics baselines are disappearing whenever we change variant configurations. We create baselines for quality gates at each milestone, but after updating variant parameters, the baselines show as empty or missing in LiveDoc snapshots.
<baseline id="QM_Milestone_2.1" type="quality-metrics">
<variant-config ref="automotive-safety"/>
<metrics>
<defect-density threshold="0.5"/>
<test-coverage threshold="95"/>
</metrics>
</baseline>
When we switch from automotive-safety to medical-device variant, the baseline disappears from the quality gates dashboard. We need these baselines to be sticky across variant changes so we can compare quality metrics between product variants. How do you maintain quality baselines that survive variant configuration updates?
We’re creating them with variant scope because the quality metrics are different for each product variant. But we need to compare metrics across variants - like comparing defect density between automotive and medical configurations. How do we make baselines accessible regardless of active variant?
This is a known issue with variant-specific baselines. Are you creating the baselines with variant scope or global scope? Variant-scoped baselines are only visible when that specific variant is active.
That helps with visibility, but what about LiveDoc snapshots? When we generate quality reports with LiveDoc, the snapshots don’t include the baseline data if the variant doesn’t match. The quality gates show as “undefined” in the reports.
You need to create sticky baselines that persist across variant switches. In the baseline configuration, set the scope to global but include variant metadata as tags rather than direct variant references. This way the baseline remains visible regardless of which variant is currently active. You can still filter by variant in your quality reports using the metadata tags.