CI/CD Pipelines: Releases, Rollbacks, and Quality Gates

Tag-based releases, canaries, rollbacks, smoke tests, migrations, and quality checks.

View

Export

Copy the compact sheet, download it, or print it.

Download

`D` dense toggle · `C` copy all

## Ship progressively

Release from version tags

on:
  push:
    tags:
      - 'v*.*.*'

# Trigger a release pipeline when a semver tag is pushed.

Canary deploy flow

./deploy.sh canary
./check-error-rates.sh
./promote-canary.sh

# Send a small portion of traffic to the new version before full rollout.

Rollback to the previous version

./scripts/rollback.sh previous

# Keep a simple rollback command or job ready before each production deploy.

## Stop bad builds from reaching users

Fail if test coverage drops below threshold

npm test -- --coverage
node scripts/check-coverage-threshold.js

# Enforce a minimum quality bar in CI.

Run smoke tests after deployment

curl -fsS https://app.example.com/healthz
curl -fsS https://app.example.com/login

# Verify critical endpoints before marking a release healthy.

Run database migrations during deploy

./scripts/migrate.sh
./scripts/deploy.sh

# Apply migrations as an explicit pipeline stage.

More in CI/CD Pipelines

No recommendations yet.