Glossary of Develocity Terms

A component that runs in CI/CD environments to collect build data and report it to the Develocity server.

A secure token used to authenticate requests to Develocity APIs.

A feature that stores and reuses outputs from previous builds to improve build performance.

A server component that stores and serves build artifacts for the Build Cache feature

A detailed record of a build, including performance metrics, dependencies, environment details, and failures. Used for debugging and optimizing builds.

Key performance indicators of a build, such as execution time, cache hit rate, and parallelism.

Develocity’s ability to integrate with Continuous Integration tools (e.g., Jenkins, GitHub Actions, GitLab CI) for build data collection and insights.

The process of collecting data from a build (e.g., inputs, outputs, environment) for analysis and diagnostics.

A performance and productivity platform for software builds and tests, formerly known as Gradle Enterprise.

A visual interface in Develocity that provides summaries, charts, and drill-down views of builds, performance, and trends.

A Develocity API that allows programmatic access to build scan and performance data for external analysis.

Develocity feature that identifies common or flaky build/test failures and helps track their frequency and root causes.

A plugin applied to Gradle builds that enables Develocity integration, such as publishing build scans or using the remote build cache.

Automated tests run by Develocity to ensure its components (e.g., cache nodes, data collectors) are functioning correctly.