Practical game day scenarios for CI/CD: broken rollbacks, permission issues, and slow feedback loops—and how we fixed them.

On this page

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

Most teams say they have a CI/CD pipeline; fewer can explain what happens when a deploy half-fails on a Friday night.

Game Day Scenario: Rollback That Never Rolls Back #

We simulated a bad deploy by merging a PR that intentionally broke a health check.

Observed:

The canary failed, alerts fired, but the pipeline stopped for manual intervention.
On-call engineers had different mental models of how rollback should work.

Fixes:

We made rollback a first-class job in the pipeline:

```yaml jobs: deploy_prod: steps: - run: ./scripts/deploy.sh rollback_prod: if: failure() steps: - run: ./scripts/rollback.sh ```

We documented one canonical rollback path per service.

Game Day Scenario: Missing Permissions #

In another exercise, we revoked a service account permission in staging.

The deploy failed halfway through, leaving stale pods.
Logs showed a generic “Forbidden” error; the pipeline reported only “step failed”.

Changes:

We added structured logging around each infra call.
We taught the pipeline to surface the exact failing command and principal.

Takeaways #

Run game days regularly; don’t wait for production to teach you.
Practice rollback as much as you practice deploy.
Make pipeline failures boring and obvious, not puzzles.

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

Game Day Scenario: Rollback That Never Rolls Back #

Game Day Scenario: Missing Permissions #

Takeaways #

Architecture Review: Blue-Green Deployment Guardrails

Log Aggregation Strategies: Centralizing Your Logs

More from DevOps

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

End-of-Week Engineering: Why Smart Tech Teams Don’t Ship Major Changes on Friday

SRE Error Budgets in Practice: Shipping Fast Without Burning Reliability

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

End-of-Week Engineering: Why Smart Tech Teams Don’t Ship Major Changes on Friday

SRE Error Budgets in Practice: Shipping Fast Without Burning Reliability

GitHub Actions for Monorepos: Fast CI Without Pipeline Chaos

Kubernetes Cost Optimization for Teams: FinOps Tactics That Actually Work

Azure DevOps Best Practices in 2026: Build Pipelines You Can Trust

About Kiril urbonas

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

Game Day Scenario: Rollback That Never Rolls Back#

Game Day Scenario: Missing Permissions#

Takeaways#

Architecture Review: Blue-Green Deployment Guardrails

Log Aggregation Strategies: Centralizing Your Logs

More from DevOps

What We Learned Running Weekly Game Days on Our CI/CD Pipeline

End-of-Week Engineering: Why Smart Tech Teams Don’t Ship Major Changes on Friday

SRE Error Budgets in Practice: Shipping Fast Without Burning Reliability

About Kiril urbonas

Game Day Scenario: Rollback That Never Rolls Back #

Game Day Scenario: Missing Permissions #

Takeaways #