The Secrets of the Build Scan Plugin and the internals of Gradle
summary
Build scans and Gradle internals turn into concrete actions: enforce JAVA_HOME to disallow multiple daemons so Android Studio and the CLI share one process; sample code uses ManagementFactory to detect 90% GC time and print a warning; a build‑operation listener reads compiledJavaBuildOperationType to measure Dagger annotation processor ms and sum slow processors; a Gradle Dr. plugin benchmarks builds (example means 68.5s vs 70.1s) and computes a threshold to benchmark remote build cache needed bandwidth so slow cache links trigger advice.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:32Welcome
- 1:07About me
- 2:10What is a build scan
- 2:57Build scan information
- 3:40Build scan data
- 3:55mismatched JDK
- 4:57reuse Gradle daemon
- 5:47Android Studio warning
- 6:13How do you get people to reuse Gradle Damons
- 6:43How to check how many Gradle daemons are running
- 8:22Gradle samples
- 9:47Multiple projects
- 10:10Java Home
- 13:00Basic Build Measurements
- 14:23The Problem
- 15:15Garbage Collection
- 16:43Garbage Collection Time
- 17:43Annotation Processing Time
- 21:49Warnings
- 22:06Callbacks
- 24:56Limitations
- 25:27Gradle API
- 26:42Log Events
- 29:25Visual VM
- 30:21Gradle Profiler
- 31:34Other cool things
- 32:41Is the Remote Build Cache worth it
- 33:55How to benchmark the build cache
- 34:16Summary
- 35:02Questions
