Did you know that Gradle Enterprise Maven Build Scans now offers a Dependencies section that visualizes the resolved dependency graph used to form the classpaths for each module. It is available for every Maven captured build, without the need to invoke a specific Maven goal. Maven dependency resolution visualization requires Gradle Enterprise Maven extension 1.4+.
Season 1 of DevProdEng Showdown is well underway with three episodes that have been viewed live or on-demand by over 6,000 viewers since our pilot episode aired in January. You can register for Episode 4 which takes place Wednesday, May 26, 2021 (10am SF, 1pm NY, 6pm London, 7pm Berlin). The topic is “Android Architecture and Developer Productivity Engineering at Scale.”
In this guest post, Roger Taracha, senior Android engineer at Premise Data, shares his company’s experience using build-cache node replication to serve their distributed teams across the globe. Roger begins with a conceptual recap of the Gradle Build Cache, its benefits, and general installation/configuratIon considerations. He then outlines the key benefits of node replication and the setup and configuration process (including connecting to Gradle Enterprise). Roger closes by sharing the inner workings of the Gradle build script solution that optimizes replicated node selection for local developer performance.
For decades, the success formula for many (if not all) breakthrough business and technology productivity methodologies has been “Productivity = Speed * Efficiency”, where “efficiency” in this case refers to the ability to maintain or even improve quality as process and workflow execution speed up.
In Gradle Enterprise 2020.5 we’ve added the missing piece to our testing product for Maven: Test Distribution (available for Gradle builds since Gradle Enterprise 2020.2). In this blog post, we’re going to connect the build of the Eclipse Jetty open source project to Gradle Enterprise. We will demonstrate how Test Distribution and Build Caching – with very little effort – reduce the total build time from over 50 minutes to about 15 minutes for a typical code change. We will also discuss potential options for reducing build time even further by optimizing the build for Test Distribution.
If some of the most important open source projects in the world are any indication, Gradle Enterprise is quickly emerging as a staple for build and test data analytics and as a source of acceleration technology for both Gradle and Maven-based builds. Spring, JetBrains (Kotlin), JUnit, and not surprisingly, Gradle Build Tool, all rely on Gradle Enterprise to improve build and test feedback cycle times and make troubleshooting more efficient with root cause analysis data (Build Scans) and failure analytics. Here’s a brief summary of the role Gradle Enterprise is playing in each project and some high-level results.
There are two primary—and complementary—approaches to improving developer productivity. Both aim to use resources more efficiently and help ship code faster, while improving the developer experience.
A modern and productive development environment should include both binary repositories and build caches.
Stash recently deployed Gradle Enterprise and is already seeing benefits. We caught up with Joel Parrish, Principal Engineer at Stash to get the low down and he shared his experience and results to date.
Gradle Enterprise 2020.2 features Test Distribution for Gradle builds and version 2020.5 added support for Maven. We have compiled this list of FAQs to supplement the information shared in our webcast: Gradle Enterprise Unveils Test Distribution.
