Gradle, the Ultimate Alligator(Delegator)
summary
Uses gradle kts to inspect Gradle internals and shows how to debug the Android task execution pipeline: run a dry run to list tasks, find that connectedCheck is implemented by DeviceProviderInstrumentationTask, attach a JVM debugger to the Gradle daemon (default port 505) after adding the plugin jar to the buildscript classpath (compileOnly or buildSrc), and use the property flag debugGradle true to pause execution. Demonstrates why the plugins block is compile-time special, how extension accessors and Provider-backed properties work, and reproduces a failing test by removing a custom test runner.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:53Build Lifecycle
- 6:43Debugging
- 11:53Build Script Runtime Class Path
- 30:01Domain Object Container
- 33:05Debugging Gradle Plugins
related talks
49mGradle plugins: take it to the next level (en)
56mDeep Dive into the Android Gradle Plugin
51mGradle Plugin, Take Control of the Build!
38mGradle Without The Guesswork: A Guide for Kotlin Developers
39mGradle + Kotlin: Basics and beyond
01h 03mKey Gradle Concepts And Practices
38mLevel up your Android build
44mGradle: The Build System That Loves To Hate You
