Develocity Artifact Cache CLI

Develocity Artifact Cache CLI caches the downloads that build tools, package managers, test runners, and code analysis tools need, plus Gradle build initialization inputs, on Edge nodes. At the start of each CI job, the CLI restores these inputs from the nearest Edge node. The build proceeds without re-downloading dependencies from the WAN or re-running initialization steps.

Key Capabilities

  • Dependency caching: stores and restores what build tools, package managers, test runners, and code analysis tools download, from Edge nodes, reducing WAN downloads on CI

  • Setup Cache: caches Gradle build initialization inputs (compiled build scripts, resolved configurations, buildSrc, and included builds) to reduce startup time on cold CI agents

  • CI-platform agnostic: runs as shell commands in any CI environment

  • Develocity integration: reports Artifact Cache and Setup Cache metrics to Build Scan® via the Common Custom User Data plugins

  • Edge-native: uses Develocity Edge nodes as the persistent cache layer, with automatic Edge discovery via access key

Using Artifact Cache requires the Artifact Cache entitlement on your Develocity license. Using Setup Cache requires the Setup Cache entitlement. For questions about license entitlements, contact Develocity support.

In This Section

User Manual
How the CLI works: operation flow, Edge discovery, and observability
Concepts
Understand the core objects the CLI works with
Guides
Step-by-step CI platform setup and observability investigations
Reference
System requirements and CLI command reference
Download the CLI
Get the CLI JAR from an Edge node or your own repository
Troubleshooting
Diagnose and resolve CLI-to-Edge compatibility check-in failures
Release History
Changelog and version history