How We Optimized Our Release Flow Using Google Play Console Release Tracks
summary
Cookpad automated Android releases so merges to master upload an APK to the internal test track and a Jenkins cron job promotes builds internal→closed→production on a weekly cadence. The flow uses fastlane/supply to read the highest track versionCode and then builds with an automated versionCode+1 and calendar-based major/minor written to version.properties; staged rollouts were removed, Firebase Crashlytics is used for post-release checks, and this reduced manual work and sped validation while leaving gaps around urgent schedule overrides and alerting.
AI-written summary · about
chapters (6)
- 0:00Release issues at Cookpad
- 6:41Adapting flow to automation
- 11:17Automated release details
- 16:32Google Play Console tracks
- 20:55Version management
- 22:53Effects and future challenges
related talks
41mRelease management: Successful launches and updates on Google Play
38mFrom Development to Production: Tips to Optimise Android App Deployments
57mThe Road to Mobile DevOps for Android
29mOur Journey to Fully Automated Weekly Releases
32mBuilding Quality Android Apps for the Future with Continuous Integration
43mSecret Sauce of Cross-platform Mobile App Continuous Delivery
24mFuture-proofing your Android release process
41mAutomating mobile applications from dev to production