Edge

Edge nodes extend Develocity services to remote locations, reducing latency for distributed teams.

Starting with Develocity 2026.2.0, a co-located Edge node is deployed alongside Develocity to provide a low-latency cache layer, without requiring separate Edge infrastructure provisioning. This co-located Edge node and any externally provisioned Edge nodes coexist: the co-located node serves the Develocity location, while external nodes serve remote locations. No data migration is needed when adopting the co-located Edge node: its cache is ephemeral and repopulated automatically from peer nodes or Develocity.

While the full lifecycle of an externally provisioned Edge node is managed in the dedicated Edge Manual, central configuration and node registration are handled within the Develocity administration using the user interface or unattended configuration.

Builds that have enabled "Edge discovery" can use the Develocity user’s location setting to automatically assign an Edge to use as a remote Build Cache. Previously, using the Develocity Build Cache node in a distributed fashion required per-user local build configuration changes. The Develocity Edge with "Edge discovery" removes the need for extra local build configuration and allows Edge locations and instances to be updated dynamically as the Develocity server manages all configuration.

Key Administrative Tasks

For detailed step-by-step instructions, refer to the following sections in the Develocity Edge User Manual:

Configure via the User Interface

To manage Edge nodes from the Develocity User Interface:

  1. Navigate to Administration  Edges.

  2. From this dashboard, you can monitor the health of Edge locations, view data transfer statistics and manage Edge node registration tokens.

Develocity Edge Administration UI
Develocity Edge Administration UI

See the Develocity Edge User Manual for detailed instructions on managing Edge nodes via the UI.

Configure via Unattended Configuration

See the Develocity Edge User Manual for detailed instructions on configuring Edge nodes via Unattended Configuration.

Technical Notes

  • Permissions: Users require the Configure Edge nodes permission to access these settings.

  • Connectivity: The co-located Edge node communicates with Develocity over the internal cluster (or host) network and requires no additional externally exposed ports. For externally provisioned Edge nodes, ensure that firewall rules allow outbound traffic from each Edge node to the Develocity server, and that build agents can reach the Edge node on its build-tool port (5071 by default). See Installing Edge nodes for the full list of ports bound by an Edge node.