CI/CD Pipeline Rollout Across a 36-Person Engineering Team
Client: Internal — Onest Tech LLC · Industry: Software Development / DevOps · Role: Tech Lead — Architecture & Rollout · Duration: 8 weeks
The Challenge
A 36-developer team across 8 concurrent projects was deploying manually via SSH. Staging was perpetually broken, deployments took 45+ minutes, and post-deploy incidents were frequent. Two previous attempts to introduce automation had failed because they tried to change too much at once, causing developers to bypass the pipeline entirely.
The Solution
Designed a phased adoption strategy over 8 weeks. Phase 1: automated testing only (PHPUnit + ESLint on every PR via GitHub Actions) — no deployment changes, just fast feedback. Phase 2: auto-deploy to staging on merge to develop using Docker Compose on a single VM — simple and debuggable. Phase 3: production deploy with a one-click manual approval gate in GitHub Actions. Each phase was adopted before the next began, building trust incrementally.
Results & Impact
- Deployment time reduced from 45 minutes to 8 minutes
- Post-deploy incidents down 60% within 3 months
- 100% team adoption — no pipeline bypasses after Phase 2
- Developer survey showed measurable increase in deployment confidence
- Onboarding time for new developers reduced by 2 days (environment setup automated)