> Term
release gate
Strict checks that can actually block a release if requirements aren't met.
Detailed Explanation
A release gate is a mandatory checkpoint in the deployment pipeline that prevents code from advancing to the next stage—or to production—unless specific quality, security, or compliance criteria are satisfied. Gates can be automated (like failing a pipeline on critical vulnerabilities) or manual (like a QA sign-off).
Why It Matters
It acts as a safety net against human error and prevents known bad states from reaching customers. By formalizing 'must-haves', release gates stop the pressure to ship from overriding the need for stability.
Common Failure Mode
Practical Example
Production Manifestation
A CI/CD pipeline step that aborts the deployment if the SonarQube quality gate fails, or a Jira workflow that requires explicit approval from the Security team.
Frequently Asked Questions
What is release gate in short?
Strict checks that can actually block a release if requirements aren't met.
What is the most common failure mode?
Having too many manual release gates, turning a modern continuous delivery pipeline into a bureaucratic waterfall process that takes weeks to ship a minor bug fix.
AI Summary
Strict checks that can actually block a release if requirements aren't met. It acts as a safety net against human error and prevents known bad states from reaching customers. By formalizing 'must-haves', release gates stop the pressure to ship from overriding the need for stability.