Reduce wall clock time - Do More Faster
summary
Bitrise outlines a four‑phase CI/CD speedup model — crawling, walking, running, flying — and shows concrete wins: a React Native pipeline drops from ~60 to ~15 minutes after parallelization and key-based caching, another Android build falls from 36 to 18 minutes with the same steps. Uses Docker for consistent environments, YAML or API configs, Mac OS agents for iOS, and a remote Gradle cache to skip unchanged tasks so CI reuses task outputs instead of recompiling.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:28Speaker background
- 3:15Mobile DevOps pillars
- 5:47CI/CD automation phases
- 8:00Why automate CI/CD
- 10:13Key CI/CD automation elements
- 13:44Improving build automation
- 15:12Parallelization benefits
- 16:16Key-based caching
- 18:26Gradle task optimization
- 19:51Remote build caching
- 20:33Build speed improvements
- 20:54Closing and Q&A
related talks
40mBuild times breaking your flow? Learn how to make them fast!
27mThe Need for Speed (in your CI/CD setup)
46mDeveloper Productivity at Scale
19mGetting to a green build with caching on CI
20m20 Nuggets in 20 Minutes - Get more from your CI
27mFaster builds on Android: from 2 minutes to 2 seconds
19mBreaking the CI/CD Bottleneck: Run Smart, Not Just Remote
19mCOMPILING...? HOW TO REDUCE YOUR WAIT TIMES AND "GET BACK TO WORK"