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
Data & Platform
Platform Engineering
Platform engineering is what stops infrastructure becoming a queue. The goal is a small set of paved paths, a new service, a new environment, a new deploy, that a product engineer can take without asking anybody.
No sales layer, no juniors. You meet the engineer before anything begins.
// What is included
What you get
- A service template that arrives with pipeline, monitoring and alerting attached
- Environments created from code rather than by request
- Sensible defaults that are hard to get wrong and possible to override
- Documentation written for the engineer who joins next month
// How it runs
The sequence
- 01
Find the queue
Which infrastructure requests recur, and what they cost in delay.
- 02
Pave
Turn the two or three most common requests into self-service paths.
- 03
Document
Written so a new hire uses it without being walked through.
// Stack
- Terraform
- GitHub Actions
- Kubernetes
- Docker
- AWS
// Related work
Where this has been done before
Client names under NDA. The numbers are not.
Production incidents down 50%+ across 26 services (NDA)
- EventBridge, CloudWatch and New Relic unified into one PagerDuty path
- Structured incident response with named ownership
- Runbooks written for the recurring failure modes
Production incidents down more than 50% across all 26 services
// Questions
Before you ask
// Also in Data & Platform
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.