Develocity Edge User Manual
Introduction
Develocity Edge makes it easier to deploy Develocity services closer to where builds are run, increasing build performance and build acceleration reliability. Edges can also act as a transparent proxy for Build Scan uploads and Model Context Protocol (MCP) requests for Develocity MCP Server and Develocity Analytics MCP Server, providing a single point of access for build and AI agents in restricted network environments.
This manual covers setting up an Edge, by creating an Edge in Develocity, installing one or more Edge nodes and connecting the node(s) to Develocity. Also covered by this manual are the steps to enable "Edge discovery" for compatible Develocity plugins and extensions to leverage the Edge network, and to configure Edge nodes to proxy Build Scan and MCP traffic.
Requirements
Develocity Configuration
To use Develocity Edge, it’s necessary to have Develocity installed.
Verify Object Storage Settings
All Edge nodes are replication-enabled, replicating data stored to and from other nodes in the Edge network, which always includes the Develocity server. This eases replication configuration, particularly when deploying a set of load-balanced nodes at an Edge location.
It’s important to review your Develocity object storage configuration ahead of Edge rollout. Check that Develocity is connected to a cloud-based object storage service like Amazon S3 or, if using embedded object storage, that it’s appropriately sized. The embedded object store volume should have at least three times as much storage allocated to it as the storage allocated to the largest Edge in the network.
See the Build Cache storage section of the Develocity Administration Manual to learn more about reserving space on object storage for storing Build Cache data.
Review the Maximum Artifact Size Limit
The maximum artifact size limit configured in Develocity also applies to all Edge nodes. Any Build Cache, Artifact Cache, or Setup Cache artifact stored via an Edge node is subject to the limit configured on the Develocity server. There is no Edge-specific setting for this limit.
See the Build Cache configuration section of the Develocity Administration Manual for instructions on how to configure this value.
Administering Edges
Establishing Edges requires configuration to be applied to Develocity, either via the Develocity Administration page or imported as unattended configuration.
Refer to the Edge Administration Using Develocity section to learn more before proceeding to install an Edge node.
Edge Node Application
To establish an Edge at least one Edge node must be installed (and connected to Develocity). An Edge node is a server application responsible for processing requests from builds that apply Develocity build agents and for replicating data across the Develocity Edge network.
| Use of Gradle’s Edge node software is subject to the Gradle Terms of Use. |
The Edge node application is distributed as a Docker image via