How-to Guide
Configure release gates
Set quality checkpoints on Releases before ship.
Objective
Set quality checkpoints on Releases before ship.
Prerequisites
- Admin or release manager access
Procedure
Open Releases
Governance → Releases.
Navigation: Governance → Releases, Remediation, or Topology. Approver roles may be required, verify permissions first.
Verification: Confirm organization and team context in the Console header before making changes.
Configure gates tab
Define thresholds and linked validation.
Navigation: Governance → Releases, Remediation, or Topology. Approver roles may be required, verify permissions first.
Verification: Note project, run, or agent IDs if you may need support escalation.
Test gate evaluation
Run release readiness check.
Navigation: Governance → Releases, Remediation, or Topology. Approver roles may be required, verify permissions first.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Release gates enforce reliability thresholds.
Was this page helpful?
