Continuous Integration at Haptik: our journey to hourly releases
summary
A concrete CI pipeline that achieves hourly releases by automating deployment of code, chat flows, ETL outputs and machine-learning models across environments. The implementation uses Jenkins and Ansible for orchestration and applies ETL and model tagging to move data and models; the talk explains automation steps, failures encountered, and measurable business value from hourly deployments.
AI-written summary · about
chapters (5)
- 0:00Hourly releases intro
- 6:08Why hourly releases
- 14:54Transition challenges
- 21:08CI success strategies
- 29:50Results and improvements
related talks
30mContinuous Integration at Haptik : Our Journey to Hourly Releases
35mMassively Continuous Integration: From 3 days to 30 minutes
27mAutomation, Innovation and Continuous Delivery
01h 01mA team's transition to Continuous Delivery
34mContinuous Integration: A Bittersweet Love Story
34mContinuous Integration
39mIt's Not Called Continuous Integration (CI) for Nothing
28mClimbing the Mountain of CI/CD: A Tester’s Tale