Bazel for Android Development
summary
Concrete claims and tools: Bazel plus Starlark replaces Gradle by making configuration parallel and cacheable, using remote cache and remote execution to distribute builds. Grab reports an automated migration tool Grazel (github com grab Grazel) that migrated a 3.4 million–line codebase incrementally and kept Gradle as source of truth during rollout. Missing Android features (data binding, resource processing) required custom rules and macros; overall result is much faster repeated builds at the cost of upfront rule-writing and repository layout changes.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:08WHAT IS BAZEL
- 7:06BAZEL BUILD CONFIGURATION
- 12:35EXTERNAL DEPENDENCIES
- 13:27PLUGINS VS RULES
- 17:29MODULE CONFIGURATION
- 18:10PROJECT LAYOUT
- 22:29MODULES VS TARGETS
- 26:17ANDROID SUPPORT
- 28:39KOTLIN COMPATIBILITY
- 30:21PERFORMANCE
- 35:07MIGRATION
- 36:30GRAZEL
- 39:00ADVANCED BAZEL
- 41:02SUMMARY
related talks
17mGrazel - A Gradle plugin to automate Bazel migration for Android projects
42mBazel
43mBoosting Bazel adoption on Android with automation
41mBazel on Android: The Good, The Bad and The Ugly
01h 12mBazel for Android Developers
41mDo You Need Bazel in Android Development?
39mAutomated migration of Android apps to Bazel build system
26mSpotify's Journey to Releasing One of the World's Largest Apps wit...