Lessons in CI_CD from 3500 Android Teams
summary
Survey of ~3,500 Android teams plus Bitrise’s 2M-build/month dataset shows median Android build time of 13 minutes on Bitrise, 86% run unit tests, 69% run static analysis, 27% run snapshot tests, 12% store pipelines as code, 38% post CI status to chat, and 19% auto-publish to Google Play. Recommendations include measuring with Gradle Enterprise or Grafana, using remote Gradle cache and parallel test runners, validating YAML with Bitrise CLI, using Espresso for screenshots, and automating Play Store uploads via Fastlane or the Google API.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:08About the speaker and Bitrise
- 4:02Key elements of mobile DevOps
- 7:38Introducing MODAS survey
- 12:13Build times and optimization
- 14:48Unit testing best practices
- 16:16Static analysis and lint testing
- 17:20Snapshot testing overview
- 18:46Build notifications in workflows
- 19:51Pipeline as code benefits
- 21:40Automating Google Play deployments
- 22:43Summary and resources
related talks
41mHow Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams
21mStreamlining Android app development and release processes
20mMaximize development efficiency with expert CI/CD strategies
21mDo more faster - Taking your Mobile DevOps setup to the next level
38mFrom Development to Production: Tips to Optimise Android App Deployments
25mMobile DevOps - How CI/CD can change your development world
25mDevOps for Android supercharged with AI
23mWalk, Run, Fly - Take your build pipeline to the next level!