Effective Gradle Scripts for Android Projects
summary
Shows concrete Gradle techniques: split a monolith into separate projects and publish common parts to a local Maven repository, use composite builds (needs Gradle 3.x) to avoid CI upload loops, centralize version strings in a root Gradle file, load keystore passwords from environment variables, use flavorDimensions to mix variants, and measure builds with profiling and the Build Scan plugin. Claims about savings include 80% unchanged code moved out. A Buck wrapper plugin is suggested as faster but is finicky and may fail in some setups.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:31GRADLE SCRIPTS FOR ANDROID PROJECTS
- 4:38Break your code!
- 6:01Module ownership is a challenge
- 6:49Create multiple smaller projects
- 11:09Composite builds
- 13:14Compose multiple random builds
- 16:39Enable single place ver. update
- 18:05Secure passwords
- 20:37Item 5: (Flavor)Dimension
- 21:50Measure!
- 22:14dependencies classpath "com.gradle:build-scan-plugin:1.1.1"
- 22:24Optimize it...
related talks
32m5 ways to improve your Android build productivity
37mBuild bigger, better: Gradle for large projects
26mGoodness, Gracious, Great Builds of Gradle
38mLevel up your Android build
40mImproving Android Build Performance
30mModular Android Development
44mA Healthy Dose of Gradle
32mGradle Convention Plugins