Develocity 2025.1

Troubleshooting failed Gradle or Maven builds using Build Scan is simpler than ever.
The summary page for a failed build now directly displays the relevant failures, guiding you to the specific test or failure page. 

In most cases, this summary will provide sufficient information to investigate and resolve the build failure efficiently. The failure page also provides direct links to test failures for Gradle test tasks or Maven test goals.

Build failure summary with multiple test failures for a Gradle build

Failure details with multiple test failures for a single Maven goal

Our new AI-powered failure grouping will give you deeper insights into the issues affecting your build stability. This beta feature groups similar build and test failures within a Build Scan, providing developers and build engineers a clearer understanding of the patterns and root causes that need attention for successful builds and tests.

This enhancement builds upon the improved Build Scan failure reporting. For Gradle task and Maven goal failures, we use AI to extract relevant log lines to determine the root cause of the failure.

Build summary with similar test failures grouped together

Build summary with relevant console log from a Gradle task failure

We have enhanced Build Scan support for npm and Python (beta) to provide richer test insights.
You can now capture, display, and share test results from popular test runners in their respective ecosystems: Jest (JavaScript) and pytest (Python).
If you require Mocha or Cypress (JavaScript) support, please contact the Develocity support team or your customer success representative.

With the test view, you can:

• Visualize the result of test processes as a whole
• Navigate to and view the results of individual test files and test cases
• Identify slow and/or flaky tests

Test view for npm and Python

The Develocity Plugin for Gradle has been enhanced with methods that allow to configure Gradle tasks that run npm or supported Python tools to produce Build Scan reports automatically.

Leveraging these reports can give you additional structured information that may not be available in a Gradle Build Scan, such as the test insights mentioned above.

Refined Reporting of Realized Test Acceleration Savings

Develocity Reporting and Visualization includes updated dashboards that facilitate understanding the usage of Predictive Test Selection and Test Distribution in your builds.

Along with observed serial and wall-clock savings, the visualization provides several key metrics to assess the feature’s effectiveness, such as the number of test classes run remotely due to Test Distribution.

A Dashboard showing “Realized Predictive Test Selection Savings”

A Dashboard showing “Realized Test Distribution Savings”

More Supported Build Tools

Develocity now provides unified observability across all supported tools (Gradle, Maven, Bazel, sbt, npm, Python).

This allows you to understand tool adoption, build performance by tool, and pinpoint areas for developer workflow optimization.

You can now easily identify Grafana dashboards based on the tools they support, as they have been tagged accordingly.

All dashboards are annotated with Grafana tags to highlight which build tools they support

The displayed data can only show builds for a specific build tool

More filtering options

Specific dashboards now support filtering the displayed data by the tags in the respective Build Scan.

This allows you to view particular subsets of the overall data to gain deeper insights into your build environment.

Tag filtering is initially supported on the following dashboards:

• Global Volume
• Project Volume
• Dependency Downloading
• Gradle CPU Usage
• Maven CPU Usage
• Realized Build Cache Savings
• Multiple “Settings” dashboards

The displayed data can now be restricted to only builds with specific tags. Multiple selected tags are combined with ‘and’ semantics

In previous Develocity versions, access keys remained valid until they were manually revoked. Starting with Develocity 2025.1, all access keys will expire automatically based on age.

Access key expiration is enabled by default, and the maximum lifespan is 365 days.

Access Keys Overview

To customize or disable the maximum lifespan for access keys, adjust the relevant settings in your values.yaml file.

Develocity Gradle plugin 4.0, Maven extension 2.0, and Test Distribution agent 3.3 introduce significant changes designed to enhance the resilience of Test Distribution.

These updates prevent build failures due to unexpected errors during communication with remote components. Develocity build plugins will now attempt to fall back to local test execution in the following scenarios:

• A build fails to establish a connection with Develocity
• A build fails to transfer files required for remote execution
• A remote agent encounters an unrecoverable error while running tests

Furthermore, Test Distribution agents that experience an unrecoverable error will no longer be assigned to new builds and will be prompted to shut down.

Please consult the Test Distribution agent documentation for information on the available mechanisms for replacing such agents.

In this release, we’ve added a new API endpoint for retrieving sbt build attributes, which allows you to (but is not limited to):

• Track how often sbt is used
• Identify the machine on which it ran
• Measure how long it took
• Discover the sbt version in use across various projects

You may leverage the out-of-the-box Develocity Reporting and Visualization dashboards to easily explore your sbt projects, build data, or export it to your preferred data analytics platform.

See Get the attributes of an sbt build in the Develocity API reference documentation for more information.

Develocity 2024.3 introduced an opt-in “Edge discovery” option for Gradle and Maven builds. This option uses the user’s location setting to assign an Edge as a remote build cache automatically.

In Develocity 2025.1, the location of the Edge used by a build for remote build caching is visible on the “Performance ->Build Cache” page of a Build Scan, along with whether the “Edge discovery” option was enabled for the build.

An example showing the used Edge cache

Develocity Edge nodes can bypass the Develocity server and directly access external object storage during replication using signed URLs.

This option reduces the load on the Develocity server, which would otherwise be responsible for streaming build data to and from connected object storage to Develocity Edges, reducing network traffic and improving scalability.

This feature is supported by both AWS S3 and Google Cloud Storage.

The Develocity Maven extension 2.0 now supports Maven 4.0.0-rc-3 and later releases candidates. You can confidently test the extension with the latest Maven RC release, knowing that we are committed to maintaining compatibility with future RC versions and the general availability (GA) release of Maven 4.0.0.

Develocity 2025.1 introduces a new metrics-gathering solution.

This updated monitoring setup represents a significant step towards a stateless application, with metrics now stored in Object Storage.

Starting with this version, Develocity enhances security by introducing a non-root user for most components.

We’ve added a new quickstart guide to our documentation to help you quickly evaluate Develocity on Amazon EC2. Effortlessly deploy Develocity and publish your first Build Scan within minutes. Please note that this guide is intended for evaluation purposes and not for production environments.