Maximize development efficiency with expert CI/CD strategies
summary
Company with 10 engineers running ~50 builds a day and 20 minute average builds uses Bitrise and Gradle to cut that time by combining three concrete changes: enable Gradle parallelization on an 8 CPU 32 GB runner and move to a 16 CPU config to save ~3 minutes, add remote build cache (measured ~35% faster, ideal ceiling 95% improvement) to shave ~2 minutes, and shard UI tests to reclaim ~6 minutes so total savings exceed the 20 minute target.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:52CI/CD time savings
- 4:06AI versus build optimization
- 8:07Gradle parallelization
- 8:28Build caching strategies
- 12:46Cache hit rates analysis
- 16:43Workflow splitting and test sharding
- 18:51Distributed test execution
- 19:34AI in CI/CD
- 20:16Q&A
related talks
20mDevelopment efficiency with expert CI/CD strategies
25mMaximize CI/CD efficiency using AI and a vertically integrated stack
24mLessons in CI_CD from 3500 Android Teams
23mWalk, Run, Fly - Take your build pipeline to the next level!
40mNail your Gradle build time
25mDevOps for Android supercharged with AI
41mHow Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams
27mThe Need for Speed (in your CI/CD setup)