From 7 to 70 Developers, How to Scale your App Release Process
summary
Lyft grows from 7 to 70 developers and then beyond and standardizes on a weekly release cadence with three branches (alpha, beta, release) to avoid ad hoc merges. The team swaps Gradle for Buck to cut incremental build times by ~3×, builds in-house tools: TCS (target/configuration service), Bubble proxy, CLI driver simulator, Launch Tracker and internal bug reporter, defines cherry-pick rules, measures impact with experiments, and reports that these systems materially reduce late merges and speed up safe rollouts.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:15SCOOP
- 6:59Release Workflow
- 16:49LYFT.APPRELEASE
- 18:27BUBBLE
- 23:00Rideshare Apps
- 27:52LYFT-CLI
- 31:40Bug Reporting
- 32:47TBS Apps
- 36:40Launch Tracker
- 39:06Summary
related talks
01h 00mAndroid builds
28mHow to ship apps better, faster, stronger
17mStreamlining Mobile Releases
44mTales of a Mobile DevOps
29mOur Journey to Fully Automated Weekly Releases
24mFuture-proofing your Android release process
21mFrom chaos to control: Future-proofing your Android release process
35mTaming a beast