I’m excited to share the news that today Gradle Inc. announced that it has acquired Triplequote and that both I and my fellow co-founder Mirco Dotta have joined the new Scala team at Gradle! If you are not familiar with Triplequote, our technology speeds up builds for Scala developers with the world’s only parallel compiler for the Scala language, called Hydra.
One of the most powerful features of Gradle Enterprise is its remote build cache. It allows teams to share the benefits of caching, even for local builds. If you have code that hasn’t changed, there’s no reason to rebuild it.
Here at Gradle, Inc., we don’t just talk about Developer Productivity Engineering (DPE). We practice it every day. We know that companies that make DPE a priority have focused, productive developers who deliver better code faster while experiencing the joy of coding. That’s why Gradle has engineering resources dedicated to ensuring our developers get the same benefits as our customers. And we eat our own dog food. (Or, if you prefer, we drink our own champagne. Then again, not all of our code is written in France, so maybe we’re drinking our own sparkling wine.) That includes using Gradle Enterprise Test Distribution.
Gradle Enterprise provides a complete look at the build system, its performance, and individual build details. We recently had a build cache node crash that was impacting build times. In this post, we’ll go through the information Gradle Enterprise generated before, during, and after the build cache node crash that made it easy to determine this was the cause of the slow build performance problem.
This is a cautionary tale about the consequences of not investing enough in Developer Experience, what to do about it if you find yourself having to address those consequences, and how to avoid getting into this situation in the first place.
The first annual Developer Productivity Engineering Summit will take place on November 2-3 in San Francisco. This two-day, dual-track event features the leading minds in Developer Productivity Engineering (DPE). The theme is “Next Practices for Transforming the Developer Experience.”
In a recent Inc. Magazine article, “Google Has a Productivity Problem That Has Stumped Managers for 113 Years. Will Sundar Pichai Be the First to Solve It?” (Aug. 2022), Pichai said the tech giant’s productivity levels do not match its growing headcount. Google executives have reportedly said they want to “get better results faster” with the people they have, and employees have been warned to boost performance or “there will be blood on the streets.”
Earlier this year, Aurimas Liutikas from the Google AndroidX team joined our DPE Lowdown webcast to talk about how Gradle Enterprise has helped them troubleshoot build and test failures faster in their GitHub Actions CI environment. Since then, we’ve heard from many companies that already use or plan to adopt GitHub Actions as their CI solution and want to understand how Gradle Build Tool and Gradle Enterprise fit into the CI build experience. In this post, we will cover the official Gradle Build GitHub action that the AndroidX team is using to integrate with Gradle Enterprise and some of the build troubleshooting best practices Aurimas shared in his talk.
In a recent DevProdEng Showdown! Android gurus from some of the most famous technology and global business brands shared their best tips for accelerating Android build and test feedback cycle times. Here is what our friends at Twich, JP Morgan Chase, Delta, and Kaiser Permanente had to say. You can watch the video segment or read their comments (edited for clarity) below.
In the course of engineering new solutions that improve developer productivity by speeding up builds and tests, Gradle will introduce new concepts and new enabling technologies. Here we will introduce and explore the concepts and technologies associated with performance consistency and performance continuity and the benefits of achieving elevated states of both. Let’s begin by defining performance consistency and contrasting it with performance continuity.
