HiveMQ started their deployment of Develocity in August 2022 and has seen multiple benefits for its mission-critical testing process. We caught up with Silvio Giebl, senior software engineer on the Platform Team, and Georg Held, director of product development, to get the low down on their experience and results to date.
Connecting hundreds or thousands of projects to Develocity (formerly Gradle Enterprise) for the first time can be challenging. The canonical way requires modifying the existing build configuration settings, which is not easily done at scale. This document explains how to use OpenRewrite from Moderne to create pull requests that will update all repositories at once.
Developer Productivity Engineering (DPE) is a practice for improving developer productivity leveraging technologies—rather than exclusively relying on traditional management best practices. This includes foremost analytic technologies for observing and collecting the many metrics and indicators of the overall health of your toolchain in terms of speed and reliability. Develocity captures, records, and presents these metrics. We wanted to learn which of these metrics are the most important, so we asked our users!
We are thrilled to announce the release of Develocity 2023.2 featuring General Availability (GA) support for the Bazel build system. This major release highlights our commitment to supporting the Bazel community, further evidenced by our recent admittance to the Bazel Products Partner program. We also announced beta support for the sbt build system, as we continue to embrace the Scala developer community.
In the dynamic world of open-source projects, the Spring Boot team, a vital part of the Java ecosystem, grappled with a challenge slowing down their progress: extensive build times. Their build process, both local and on CI, would take an hour or more, affecting their productivity. The turning point? The deployment of Develocity.
In this blog post, I will walk you through the highlights of this journey and provide the transcript of my interview with Andy Wilkinson, staff engineer at VMware and Spring team developer, from which this piece is based.
Develocity automatically observes, records, and reports details about your CI builds. This information provides the basis for generating performance and failure-related insights and developing metrics to make CI pipelines more efficient. This automation allows CI and DevOps Engineers to focus on sustained improvement instead of tech support. In this article, we’ll define some of those key CI metrics and explore real-world examples of Develocity helping teams to optimize CI performance and failure recovery using those metrics.
One of the most powerful features of Develocity 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.
Earlier this year, Aurimas Liutikas from the Google AndroidX team joined our DPE Lowdown webcast to talk about how Develocity 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 Develocity 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 Develocity and some of the build troubleshooting best practices Aurimas shared in his talk.
Roberto Perez Alcolea of the Netflix JVM Ecosystem team recently shared some of his team’s use cases and best practices for using Develocity to manage Gradle plugins in their builds. The Nebula project itself is a set of Gradle plugins that eliminate boilerplate build logic and provide sane conventions for simplifying build scripts.
At Netflix, improving developer happiness is a goal of paramount importance since it is highly correlated with developer productivity. Netflix Engineering has experienced significant benefits from their investments in improving the developer experience and productivity by using automation, tools and data rather than by management decree and best practices. This article highlights their success using Test Distribution to speed up test cycles by over 12X and provides many other productivity insights.
Accelerate
Troubleshoot
Observe
