Quality gate history
Quality gate history helps you monitor guardrails adherence and understand whether your project is actually following its configured quality gate over time.
Last updated
Was this helpful?
Quality gate history helps you monitor guardrails adherence and understand whether your project is actually following its configured quality gate over time.
A quality gate only protects your codebase when teams respect it during development and release workflows. This feature adds visibility into releases that happened while the quality gate was failing, so you can spot risky practices and improve your delivery process.
This feature is available only for projects that use the Previous version new code definition.
The feature focuses on the main branch only. It provides a project-level view of quality gate history across released versions, including:
Period filters for 30 days, 6 months, 1 year, and All time.
A summary of safe versus risky releases.
Whether each release was safe or risky at release time.
A timeline of released versions.
A release is considered risky when the quality gate was failing at the time the version was released.
This view helps engineering managers and DevOps leads identify when code is being promoted despite failing the quality gate. Repeated risky releases can indicate that guardrails are configured but not enforced in practice.
If you see risky releases, review your delivery workflow and CI configuration. You can configure your CI tool to Failing a pipeline job when the quality gate fails, which helps prevent risky releases from being promoted.
Last updated
Was this helpful?
Was this helpful?