Ignite: How CI/CD helped us "Bill Pay team" to deliver features faster to customers
summary
Consolidating scattered Bill Pay services into a single Bill Pay team microservice and wiring GitHub commits to automated pipelines on AWS cuts release cadence from monthly to multiple deploys per day, with component and integration test stages, automatic change orders and a blue-green switch for zero-downtime rollouts. The team uses Chef with python scripts, AWS, and GitHub; result is smaller change sets, fewer defects, instant production readiness and measurable faster feature delivery.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:50Integration
- 1:20USPS
- 1:35Why CICD
- 1:50Delivery Process
- 2:05State Deployment
- 2:20Production
- 2:50Quality
- 3:05Component Tests
- 3:20Integration Tests
- 3:35Production Release
- 3:50Pull Request
- 4:05Deployment Pipeline
- 4:20Benefits
- 4:50Technology stack
related talks
38mAccelerating innovation through AWS Cloud technology
33mThe Road to Enable DevOps Within the Payment Industry
30mOur Continuous Delivery Journey
39mRemove your Testing Bottleneck with CI/CD Pipelines
55mBridging the Gap Between Ops and Developers with CI/CD
26mDevOps and Lean in Legacy Environments
24mCI/CD Best Practices to Deliver Software Faster
06mIgnite - Blue Green Deployments Using Terraform + Packer + Jenkins