Improving Developer Experience with Gradle Build Scans
summary
Shows how Gradle Build Scans capture full build metadata (console, test reports, timeline) and speed triage by sharing a unique URL and using the d-scan command; points out a real build with ~5,000 tasks and only 38% cache hits, garbage collection costing 8 minutes on a 17-minute build (rule of thumb: GC >5% merits investigation). Explains local vs remote build cache, Gradle Enterprise hosting, and artifact-transform visibility requirements (GE 2023.1, plugin 3.13, Gradle 8.1).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:55What is a build scan?
- 8:57Live demo of build scans
- 21:06Investigating build slowdowns
- 33:45New artifact transforms feature
- 39:50Resources and closing
related talks
36mImproving Android Developer Experience with Gradle Build Scans
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
36mImproving Gradle Builds
43mThe Secrets of the Build Scan Plugin and the internals of Gradle
01h 39mWorkshop: Maximize Developer Productivity with Fast and Reliable Gradle and Maven Builds
41mKeeping your team's Gradle builds in top shape
37mImproving developer productivity with Gradle Enterprise in 2023
40mDeveloper Productivity Engineering for Open-Source Communities
