How Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams
summary
Aggregated Bitrise data from 3,500+ Android teams shows a median PR build 13 minutes with a third under 10 and two thirds under 20; teams speed this up using the Gradle profiler, Android’s build‑optimizing docs, caching and targeted hardware benchmarking. Survey highlights: 86% run unit tests and 69% use static analysis, yet only ~22% use the Android lint step and ~4% use Detect; snapshot testing is at about 25%. Around 38% post Slack build notifications and roughly 19% automate Play Store publishing.
AI-written summary · about
chapters (12)
- 0:00Introduction to CI/CD
- 3:40What is CI/CD?
- 5:26Data sources for analysis
- 7:52Build times in CI pipelines
- 12:44Techniques to speed up builds
- 18:02Unit testing adoption
- 20:10Snapshot testing overview
- 24:31Slack notifications in CI
- 27:21Pipeline as code benefits
- 31:37Static analysis tools
- 38:04Automating Play Store publishing
- 39:49Summary and call to action
related talks
24mLessons in CI_CD from 3500 Android Teams
21mStreamlining Android app development and release processes
25mDevOps for Android supercharged with AI
38mFrom Development to Production: Tips to Optimise Android App Deployments
34mPractical tips for succeeding with CI/CD for Android
21mDo more faster - Taking your Mobile DevOps setup to the next level
20mMaximize development efficiency with expert CI/CD strategies
25mMobile DevOps - How CI/CD can change your development world