Artifact Transforms

on YouTube ↗38m

" summary

A Gradle/Android build often runs far more transformation work than tasks: an assembled debug can execute ~5,000 artifact transforms versus ~2,000 tasks, and the Kotlin and Android plugins register dozens of transform types. Investigations show a single dependency producing 11,000 classes and ~30 MB makes a single transform taking 2 minutes, removing that library cuts the task’s transform time by 50% and yields 15% overall build time reduction; a 321-module project shows transform explosion that disabling a Hilt test option trims by ~7%. Tools: Gradle, Android Gradle Plugin, Kotlin plugin, DevVelocity/Build Scans, Grafana.

AI-written summary · about

" chapters (9)

1. 0:00Artifact Transforms intro
2. 4:03Why transforms matter
3. 10:54Custom transform creation
4. 14:51Transforms in Android builds
5. 23:18Optimizing builds with transforms
6. 32:09Fingerprinting time and scans
7. 34:19Dev Velocity API insights
8. 36:45Analyzing transform performance
9. 37:06Resources and closing

" related talks

• 30mImproving Android Build performanceTony Robalik · droidCon NYC 2018
• 37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and GradleNelson Osacky, Etienne Studer · Droidcon London 2023
• 40mMake The Android Gradle Plugin Work For YouAdarsh Fernando, Izabela Orlowska, Amr Affify, Maksim Lazebnik · droidcon London 2019
• 36mWhat's new in the Android Studio build systemJerome Dochez, Xavier Ducrohet, Leo Sei · Google I/O 2019
• 33mIMPROVING ANDROID BUILD PERFORMANCEStefan Oehme · droidcon Berlin 2018
• 40mImproving Android Build PerformanceVolker Leck · droidCon Berlin 2019
• 37mBuild bigger, better: Gradle for large projectsAurimas Liutikas, Xavier Ducrohet · Google I/O 2019
• 48mOptimizing Android Build PerformanceHans Dockter, César Puerta · droidcon San Francisco 2017