Jenkins to CircleCI: 12 pipelines migrated (NDA)
- All 12 pipelines migrated from Jenkins to CircleCI
- Reusable Terraform pipeline with auto-approve and manual gates
- GitHub Actions OIDC federation into AWS
12 pipelines moved off self-maintained Jenkins
DevOps
Release Engineering
Teams that are afraid of Friday releases are not lacking discipline, they are lacking a way back. Release engineering is the work of making a deploy reversible, observable and dull.
No sales layer, no juniors. You meet the engineer before anything begins.
// What is included
What you get
- A promotion path from staging to production with a clear gate
- Rollback proven by running it, not by writing it down
- Database changes separated from code changes so they can move independently
- Deploy visibility: who shipped what, when, and what it did to the graphs
// How it runs
The sequence
- 01
Observe
Instrument the deploy so you can see its effect before you trust it.
- 02
Separate
Split schema changes from application changes.
- 03
Rehearse
Run the rollback in staging until it is boring.
// Stack
- GitHub Actions
- CircleCI
- Terraform
- Docker
- New Relic
// Related work
Where this has been done before
Client names under NDA. The numbers are not.
Zero-downtime Redis to ElastiCache migration (martech SaaS, NDA)
- Replication-based sync kept both caches current
- Circuit breaker in the application path to fail safe
- Traffic cut over in stages, verified at each step
0 minutes of user-facing downtime
// Questions
Before you ask
// Also in DevOps
Related services
Talk to the engineer who would do the work
A 20 minute call. You describe your setup, you get an honest read on whether this helps, and the top risks worth looking at first.