Overview

A release gate evaluates reliability signals (run outcomes, Test Health, reliability scores) before software promotion. Failed gates block deploy jobs in CI when integrated via API or CLI, or require explicit approver override in Console.

Who should read this

New users, technical writers, and integration engineers aligning internal documentation with Zof terminology.

Prerequisites

Basic familiarity with Zof Console navigation
Organization member access

When to use this workflow

Onboarding engineers unfamiliar with Zof terminology
Writing internal runbooks that align with Console UI labels
Mapping customer CMDB or ITSM fields to Zof entities

Step-by-step procedure

Define gate criteria

Governance → Releases → attach suites and minimum pass thresholds.

Map staging vs production gate strictness in policy packs.

Wire CI/CD

Use /docs/examples/release-gate-api or zof run --wait before deploy stage.

Store gate ID and API key in CI secrets.

Key concepts

Release gate: Policy checkpoint evaluating reliability signals before software ships.
Where to find it: Governance → Releases

Best practices

Match Console UI labels in internal documentation for reduced onboarding friction
Link requirement and test IDs when traceability is required for audits
Do not conflate similar terms (e.g., test run vs test result vs test case)