CASE 137 · JOLLY · 2024
Forty Jenkins pipelines, off two on-prem servers in twelve weeks.
An aerospace contractor ran 40 Jenkins pipelines on two on-prem servers that had become a single point of failure (and a single point of CVE management). We migrated to AWS CodeBuild with a careful pipeline translation, and retired the Jenkins boxes.
Aerospace contractor
MIGRATION
2024
RESULTS
What changed, by the numbers.
CI INFRASTRUCTURE
AWS-MANAGED
PIPELINES MIGRATED
40
CVE PATCHING BURDEN
GONE
BUILD QUEUE TIME
−74%
HOW IT WENT
The on-prem Jenkins boxes had become a millstone — they ran on a Linux distribution two major versions out of support, with a Jenkins instance that hadn’t been upgraded since the engineer who built it had left. Every CVE alert triggered weeks of careful patching.
We translated each Jenkinsfile into a CodeBuild project plus CodePipeline orchestration. The handful of Jenkins-specific patterns (custom shared libraries, complex parallel stages) ran through a transitional Jenkinsfile-Runner step inside CodeBuild until we’d rewritten them properly.
Twelve weeks from kickoff to last pipeline migrated. The on-prem servers were powered off, then retired. CVE patching for the CI infrastructure became AWS’s problem. Peak-hour queue time dropped 74% because CodeBuild scales transparently in a way two servers couldn’t.
RELATED · SAME DOMAIN
Other engagements in this space.
READY WHEN YOU ARE
Let's get your AWS bill (and architecture) in order.
The discovery call is free. You walk away with at least one concrete idea — even if we never work together.