Create Elegant Builds At Scale With Gradle
summary
Shows concrete wins and roadmaps: LinkedIn moves Gradle and cuts a 30 day release cycle to two releases a day with 2,000 developers, ~300,000 weekly executions and 31,000 releases; demon reuse, incremental up‑to‑date checks and continuous mode demonstrably speed developer feedback; new configuration/modeling (managed types, variant-aware dependencies, compiler avoidance) reduces unnecessary recompiles; composite builds, IDE import and an Eclipse plugin work in demos; a distributed cache and build-collaboration service are prototyped and promise further gains.
AI-written summary · about
chapters (43)
- 0:00Introduction
- 0:47History of Gradle
- 1:19Build Happiness
- 2:06Gradle Domains
- 3:04Gradle Scripts
- 3:23Build Infrastructure
- 3:36Broken Build Process
- 3:59Project Size
- 4:40Complexity
- 5:31LinkedIn
- 6:31Oak
- 7:06Performance
- 8:32General
- 9:20Demon
- 10:35Enable Demon
- 11:36Incremental Build
- 13:43Continuous Build
- 16:17Substitution Rules
- 18:16Android Studio
- 19:29Gradle Improvements
- 20:17Gradle Configuration Model
- 25:09Modelling
- 25:48Service
- 26:50API
- 28:17Variants
- 30:14Components
- 31:02Platform
- 31:25Compiler Avoidance
- 31:58Example
- 36:36Company Standards
- 37:20High Level DSL
- 37:50Product DSM
- 38:24Alpha
- 41:11Conflicts
- 43:01Gradle Policies
- 44:21Custom Gradle Distribution
- 45:29Cradle
- 46:44Backend
- 46:58Project Substitution
- 48:28Distributed Cache
- 48:57Build Collaboration Tool
- 49:52Greater Summit
- 50:10Thank You
related talks
01h 01mGradle 3.0 and beyond
40mDeveloper Productivity Engineering for Open-Source Communities
33mKeeping your Gradle builds in top shape
37mImproving developer productivity with Gradle Enterprise in 2023
01h 59mGradle: Give Your Build Some Love and It Will Return It!
02h 42mHeading to Gradle 9
36mImproving Gradle Builds
27mComposite Builds with Gradle