The path to build happiness
Who is this presentation for?
- Build engineers, build-responsible developers, and engineering management
In a healthy DevOps culture, everyone is a part of the release process, but that’s not always the case for builds. Sometimes the developers own it. Sometimes the ops team owns it. In many organizations, no one owns it. Because of this, engineers (Jenn Strater included) have grown complacent with inefficient builds and even joke about how bad build times are. Now that she works as a developer advocate and teaches others about build tooling, she realizes that many of the habits she developed as a software engineer are incredibly inefficient.
Join in to learn tool-agnostic steps to achieve build happiness, including measuring your builds, analyzing the data to see how developers and CI systems are running builds, improving build processes using build automation tooling, optimizing builds with incrementalization and/or parallelization, and iterating to maintain build happiness.
- Experience with how software is built and the associated pain of cryptic error messages and flaky tests
What you'll learn
- Learn how to use data to better debug build errors and speed up individual runs, making the release process a happier experience for everyone
Jennifer “Jenn” Strater is a developer advocate for Gradle. She’s the owner of the Groovy Community slack and a contributor to various open source projects including Spring REST Docs, Codenarc, Groovy, and Gradle.
Premier Diamond Sponsor
For conference registration information and customer service
For more information on community discounts and trade opportunities with O’Reilly conferences
For information on exhibiting or sponsoring a conference
For media/analyst press inquires