Minutes to seconds: maximizing incrementality
Gradle Summit
Palo Alto · June 22 - 23, 2017
About this Presentation
Nobody likes slow builds. It easily becomes frustrating when we, as developers, know that the build tool is doing more than it should. Why would you run clean if all you need is a single class to be recompiled? Why would you even try recompile if the change you made is irrelevant to the compiler?
In Gradle 3.4, we significantly improved incremental compilation, as well as modeling your Java application, in order to minimize build times. In this talk, you'll learn how to leverage the new java-library plugin to avoid leaking dependencies, reduce your build times and make publication safer. You will also learn what “compile avoidance” means, in particular what it means in terms of modeling, and how to make your tasks incremental. We will also give you hints at what the future looks like: faster, more precise, incremental and reproducible builds.
——
Gradle Performance Team Engineer
Cédric Champeau is a software engineer at Gradle, Inc. , where he is currently focused on improving the performance of the build tool. He is also a core committer of Apache Groovy and spent more than 3 years developing full time the language at Pivotal, where he implemented features like the static compiler, traits, Android support, AST transformations or type checking extensions.
Prior to that, he spent several years in the industry as a user, where he used Groovy in multiple industrial contexts including DSLs for natural language processing, scripting or even workflows.