CI/CD Maturity Assessment
Closing the one gap that mattered across a 35-repo engineering org
Overview
Ran a structured CI/CD maturity assessment across a 35-repository enterprise financial services GitHub organization, surfacing a critical deployment-automation gap and delivering a modernization proposal that leadership accepted.
The Problem
The organization actually had a solid CI foundation β automated tests, security scans, and container builds ran on every pull request. The real gap was further downstream: there was no automated deployment trigger connecting approved, tested code to an actual environment deployment. Releases were fully manual, unscheduled, and dependent on individual availability. Quality gates existed but were configured report-only, so a failing scan or test didn't block a merge or a deployment. One service group, the AWS Lambda functions, had no CI pipeline at all β no tests, no scans, no build process.
The Solution
I built an automated inventory across all 35 repositories covering pipeline coverage, branch protection, and primary language, then deep-reviewed 7 of the most actively maintained repos end to end β full pipeline configuration and git history. I ran a structured working session with the client's engineering and delivery teams to validate the findings against real operational constraints, then scoped a proposal: automated deployment triggers on merge to the stable branch, release and environment traceability, enforcement-grade quality gates that actually block on failure instead of just reporting, and a foundational CI/CD pipeline for the previously uncovered Lambda services. Separately, in the same engagement, I found a production Aurora MySQL Serverless v2 cluster that had drifted outside IaC management and resolved it with a CDK stack matching the original cluster identifier under a retain policy, restoring IaC ownership with zero data disruption.
The Results
The 35-repo inventory and 7-repo deep review were delivered, and leadership accepted the modernization proposal. The Aurora cluster was brought back under CDK management with zero data disruption, and the infrastructure drift was fully documented.
Key Takeaways
A CI pipeline that runs checks isn't the same as a CD pipeline that acts on them β report-only quality gates are a false sense of security
The highest-value finding in an assessment is often not the exotic one β a missing deploy trigger across 35 repos mattered more than any individual pipeline's sophistication
Scoping matters as much as the findings β staying inside the boundaries of infrastructure you actually own keeps a proposal credible and actionable
IaC drift recovery β bringing a live resource back under management with a retain policy β is a precise, high-stakes operation; zero data disruption is the only acceptable outcome
Tools & Technologies
- GitHub Actions
- AWS CDK TypeScript
- Aurora MySQL Serverless v2
- CodeDeploy