Walk, Run, Fly - Take your build pipeline to the next level!
summary
Claim: an Android CI build drops from 45 minutes to 1 minute 23 seconds by using a remote build cache and incremental task avoidance. Uses Gradle (or Bazel for larger mono-repos), parallelized workflows, dependency caching and a CDN-backed remote build cache with gRPC streaming to reduce latency across regions. Notes: Bazel migration typically takes 3–4 months and needs team ownership; parallelization often halves wall-clock time; SSD reads vs in‑memory tradeoffs matter; Bitrise supplies managed runners (M1/M2) and CDN placement to make the cache practical.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:12About the speaker
- 3:17Why automate builds
- 6:48Parallelizing builds
- 8:33Dependency caching
- 11:03Advanced build systems
- 16:20Bazel setup effort
- 17:02Cache optimization challenges
- 21:03How Bitrise helps
related talks
17mBoosting your Android CI through integrating Build Cache
19mGetting to a green build with caching on CI
20mMaximize development efficiency with expert CI/CD strategies
21mStreamlining Android app development and release processes
41mSpeeding up Jenkins, Gradle, and Maven with a Build Cache
24mFaster Builds With Remote Execution and Caching
24mLessons in CI_CD from 3500 Android Teams
54mFrom Laptop Builds to Advanced CI