Avoid Build Disasters with Gradle and Gradleware
Maybe you've seen it, maybe you haven't, but a bad build can be a disaster for any organization. Builds that take an unreasonable amount of time to run, builds that force you to make bad decisions and use the equivalent of duct tape during a release process - this session is going to focus on some of the common problems with builds and how to avoid them.
This session is going to focus on some of the common maladies of build systems and how to cure them with Gradle. We'll discuss the following issues and provide solutions based on Gradle:
“Forever Builds” are builds that take an unreasonable amount of time during a release cycle. These builds are often a very visible form of failure during a high-profile release. If you've had a client or a co-worker ask you why the build was taking forever, will show you some common culprits.
Overly complex multi-module builds. Certain build tools force developers into a corner. While they might have only been interested in creating an agile prototype of a larger system, tools like Maven demand the creation of several inter-related project when one would have done the job. Find out how Grade can help.
Multi-language builds that view the world through the lens of Java. We'll discuss how Gradle can create multi-language and multi-platform builds that don't force you to make compromises.
Learning a new build tool and understanding best practices. Tim will discuss the various strategies for converting not only your build to Grade but converting your organizations to Gradle. What is the best way to make sure that your people have the skills to successfully move to Gradle.
As the author of several popular Maven books, O'Brien brings a unique perspective to the subject of migrating build systems from Maven to Gradle. He'll offer some specific advice for build engineers who need to support both Maven and Gradle builds.
About Tim O'Brien
O'Brien is a frequent speaker, presenting talks on open source publishing, open source community, and the intersection of development and marketing at such conferences as O'Reilly Strata, Oracle's OpenWorld, ApacheCon, and the Open Source Bridge conference. He has worked as an enterprise architect for financial news providers including TheStreet.com and Forbes.com, and created information architectures and content models for product comparisons at ConsumerReports.com.
O'Brien has authored and contributed to several books for O'Reilly including the Jakarta Commons Cookbook, Harnessing Hibernate, Maven: A Developer's Notebook, and Maven: The Definitive Guide. Through his work in both the publishing industry and the open source community, O'Brien has advocated an “open book” approach to technical documentation that emphasizes audience participation and the free distribution of information over traditional approaches to “dead-tree” publishing. His views on open source books are captured in a quote, “Why limit yourself to selling 8,000 books to developers when you could have half a million unique readers?”
More About Tim »