Session
The Secrets of the Build Scan Plugin and the internals of Gradle
Build scans provide some very useful information about Gradle Builds. Build time, configuration time, task execution time.
Scans even show garbage collection time, time spent downloading dependencies, time spent in annotation processors? What can you do with all this data?
In this talk I'll share how to surface actionable information from your Gradle build immediately to developers without using the build scan plugin or Gradle Enterprise.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top