CI/CD Pipeline Across 4 Environments with Jenkins
DevOps & Automation
A CI/CD pipeline is not just automation — it is a contract between developers and operations. This is the multi-environment Jenkins pipeline design I built at Genpact that reduced deployment cycle time from days to under two hours.
Key Patterns & Steps
- Environment progression: DEV → SIT → UAT → PROD. Each promotion is a deliberate gate, not automatic propagation
- Pipeline as code: Jenkinsfile in source control — pipeline changes reviewed like application code
- DEV: triggered on every commit to feature branches; runs unit tests and static analysis
- SIT: triggered on merge to develop; runs integration tests against deployed services
- UAT: triggered manually after QA sign-off; runs smoke tests and generates deployment artefact report
- PROD: triggered manually with dual approval; deploys the exact artefact promoted from UAT — no rebuilds
- Rollback: every deployment records the previous artefact version; one-click rollback in Jenkins re-deploys it
Lessons Learned
The pipeline that failed in production was the one where PROD built from source instead of promoting the tested UAT artefact. Immutable artefacts promoted through environments — never rebuild at the PROD stage.
Technologies
← Back to Architecture Notes