Gradle 3.0 and beyond
summary
Gradle 3.x adds concrete tooling: continuous builds watch task inputs and rebuild on file changes, TestKit provides a public API for functional testing of build logic, and the daemon runs by default to avoid JVM startup costs. Composite builds let projects substitute source for published artifacts, and a distributed build cache via Hazelcast shares task outputs across machines—CI times drop dramatically (examples show builds shrinking from ~17 minutes to ~1 minute). Early Kotlin support arrives as the Kotlin Gradle DSL, and build scans publish per-build diagnostics.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:45Gradle releases
- 4:05Continuous builds
- 6:25Documentation markdown
- 8:45Testkit
- 15:50Reduced configuration time
- 17:58Performance improvements
- 22:01Cotton
- 24:29Kotlin
- 24:58Gradle 300
- 25:33Gradle Kotlin
- 26:55Composite bids
- 28:07Thirdparty dependencies
- 33:33Incremental builds
- 35:44Cleanup tasks
- 38:18Share artifacts
- 40:31CI infrastructure
- 40:57speed
- 42:02what builds
- 42:46sharing builds
- 43:06optimizing performance
- 43:55using builds correctly
- 44:49great boot scans
- 49:10build skin
- 52:17future plans
related talks
51mCreate Elegant Builds At Scale With Gradle
39mGradle + Kotlin: Basics and beyond
01h 59mGradle: Give Your Build Some Love and It Will Return It!
48mWhat's new in Gradle 5?
58mGradle: Harder, Better, Stronger, Faster
01h 03mKey Gradle Concepts And Practices
31mGradle in Android Studio 3.2 and beyond
05mOver the Ant Hill to Gradle