Gradle Worst Practices: Common anti-patterns in Gradle builds

Track: Tools
Skill Level: Intermediate
Room: Room A313
Time Slot: Thu 2/23, 2:30 PM
Tags: software automation , build automation , gradle , continuous delivery , continuous integration

So you’ve learned Gradle, you’ve converted your build, and you’re project is now happily running Gradle builds everywhere. You’re done, right? Maybe not. There are common mistakes that many Gradle build authors make that can have a serious impact on performance, maintainability, or user experience. We’ll talk about some of these anti-patterns and the best ways to fix them.

This presentation is geared towards intermediate Gradle users. We’ll show some examples of these common pitfalls and use live demos to demonstrate proper solutions. We’ll begin with some simple, well-known errors and then build towards more advanced, subtle mistakes. We’ll also highlight some higher order concepts that can help avoid similar issues in your future builds.

Gary Hale

Gary is a software engineer focused on creating efficient software delivery practices. He is an IT generalist with over 15 years experience in software development, operations, architecture and everything in between.

Gary is a Principal Engineer at Gradle Inc. and is the author of the Gradle Jenkins plugin and the Gradle Glu plugin. He regularly conducts training classes on Gradle and speaks on topics related to devops, software development, and project automation.

Have a Question