Read a Release Gate

5 questions0m 0s

Learn the skill

A pipeline can automate build and test steps. A release gate blocks deployment until required checks pass. A staging environment supports checks before production. Rollback may restore old code, but it does not automatically undo database changes. Secrets belong in private configuration.

Worked example

Build passed but a required data test failed: the gate stays closed. Restoring an old program after a database format change may not restore compatibility. Plan a backup and a tested recovery procedure before a risky migration.

Build passed. Unit tests have 18 passes and 2 failures. The staging smoke test has not run. Required checks are incomplete. — Fix failures and complete required checks before releasing.

Fictional Pipeline

Build: pass. Unit tests: 18 passed, 2 failed. Staging smoke test: not run. The policy requires all unit tests and the staging smoke test to pass before release. An API key must not appear in source files, browser code or logs. This is a paper review, not permission to run commands on production.

Question 1 How many unit tests ran? Answer

Question 2 What percentage of unit tests passed? Answer

Question 3 Does this release meet the stated gate? Yes; a majority passed No; tests failed and the staging check has not run Yes; a successful build is sufficient

Question 4 What must be considered before rolling old code back over a changed database? Whether the old code still understands the data Only the button color Whether monitoring can be removed

Question 5 Where should the API key belong? A public JavaScript file A screenshot in the repository Private configuration excluded from public code and logs