Journey to painless releases: Continuous delivery for Philips Hue Android
summary
Philips Hue Android moved from ten-week releases to continuous deployment using automated CI, Docker-based reproducible builds, and Google Play auto-uploads with canary rollouts and feature flags. They slimmed instrumentation and integration tests to cut build time from ~20 to 5 minutes, enabling small pull requests, fast hotfixes, a stable master branch, and far fewer user-facing regressions.
AI-written summary · about
chapters (9)
- 0:00Continuous delivery intro
- 3:16Painful release cycles
- 9:17Feature branches vs merge conflicts
- 15:16Automating testing & cycle time
- 23:05Stabilizing master branch
- 31:54Impact assessment & quality
- 37:12Testing automation & teamwork
- 42:10Results & benefits
- 44:41Q&A
related talks
30mOur Continuous Delivery Journey
26mContinuous Everything in Mobile
38mFrom Development to Production: Tips to Optimise Android App Deployments
46mContinuous Delivery for Native Apps
30mContinuous Integration at Haptik : Our Journey to Hourly Releases
32mBuilding Quality Android Apps for the Future with Continuous Integration
50mRelease & Iterate Faster: Stop Manual Testing
01h 02mThe Road to continuous deployment