Developer Productivity Engineering Blog

Develocity 2023.4 caps a strong year of product innovation for the engineering team at Gradle along  three key dimensions. First, this year we expanded the market surface area for Develocity with GA support Bazel and sbt (in beta).

As Develocity continues to scale its footprint in large deployments, enterprise expectations in areas like high availability and security continue to rise. We are pleased to introduce the newest release of Develocity 2023.3, bringing streamlined project management with project-level access control, additional cloud integration capabilities, highly available build caching, and more. Let’s delve into the new features awaiting you.

Gradle recently had an opportunity to optimize the cloud storage layer used for Build Scan®, a feature of Develocity. In this article, we’ll deep dive into the  challenge we faced with inefficient cloud storage, our decision to migrate to Amazon S3, and the remarkable result: a 75% reduction in data storage costs.

Develocity 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: Develocity Unveils Test Distribution.

Although ephemeral builds can be nice to test changes in isolation, there are trade-offs for doing so. One of those trade-offs is dependency download times.

In Develocity 2019.3, the dependency download metrics in the performance and trends dashboards can be used to look at dependency download times and debug issues. For example, let’s look at the dependency download times for the Gradle project itself for all builds run in the last four weeks.

Changing one dependency declaration can have unexpected side effects through its transitive dependencies. For an example of tightly-coupled dependencies, let’s look at a simple Spring Boot project with the following build.gradle file.

Have you ever had an infrastructure failure break your build, or perhaps been forced to stop working in order to fix broken build configuration? Changes to development infrastructure often happen unbeknownst to the engineers it serves. Many problems go unreported, but chip away at our productivity much more than we realize. It is important to identify and stop non-verification failures (those not caused by routine development, such as compile and test failures) before they disrupt your organization. To combat this, we are pleased to introduce new failure analysis tools.

Do you ever watch your IDE sync or build run and think to yourself: “This is slow. I think this used to be much faster”? I do, more often than I’d like to admit.

Build logic can grow as complex as application logic and because of that good tooling is key for a productive build-logic authoring and maintenance experience. In this webinar, Paul Merlin and Rodrigo B. de Oliveira from Gradle explain how the Gradle Kotlin DSL leverages the Kotlin language and its great tooling to provide just that.