Build Systems & Package Managers

Native events from every build across your polyglot toolchain — captured as first-class build data, queryable end to end.

Try Develocity Free Request a Demo

Develocity Build Scan list with build-tool and build-tool-version columns and search filters, showing builds captured across the toolchain.

Feature overview

Build Systems & Package Managers

Develocity instruments every build and package-manager run from the inside, recording each as a single Build Scan — not log lines scraped after the fact, but the execution itself: task and goal execution, test results, the resolved dependency graph, version conflicts, timestamps, and input hashes. That same record spans a polyglot toolchain. Every event flows into the Observability Data Platform and feeds the Context Engineering Layer, so the data is queryable, comparable at scale, and ready for the agents that reason over it.

Works great with

One rich model across build systems and package managers — captured from inside the build, not from its logs

Every Build Scan captures what no log holds — cache keys, input fingerprints, resolution decisions — taken directly from the build, not parsed from its output.
Today that model covers Maven, Gradle, npm, Python, Bazel, and sbt — build systems and package managers alike.
The record is extensible, too — attach custom values and tags to capture context the build can't know, programmatically and non-intrusively.
The same structure on every tool — not each one's own log format, but one predictable model your queries, tooling, and agents target at once.

View documentation

A Build Scan task-execution view with build-cache coverage and timeline, representative of the depth each build-tool integration captures.

Capture Docker builds from BuildKit's own event stream

RoadmapEvery BuildKit-backed build — whether through the Docker CLI directly, Buildx, or Compose — publishes a Build Scan with timing, base images, output digest, and failure details.
RoadmapEach build step shows cached versus rebuilt, so layer-cache regressions surface per build instead of hiding in aggregate timing.
RoadmapA read-only observer subscribes to BuildKit's API — no Dockerfile edits, no build wrappers, no command changes, both locally and in CI.
RoadmapProvenance and Software Bill of Materials (SBOM) attestations attach when enabled, extending supply-chain visibility to base images and installed packages.

Develocity Build Scan list filtered by build tool, showing docker build invocations as Build Scans alongside Gradle, Maven, sbt, npm, Python, and Bazel builds.

One ingestion path for tools without a native agent

RoadmapA tool with no native agent publishes a self-describing payload — its Build Scan carries the same first-class attributes as an instrumented build: duration, requested tasks, tags, custom values.
RoadmapAn existing OpenTelemetry exporter connects for zero-code ingestion; the native API publishes richer, explicitly linked events — at whichever depth the tool already supports.
RoadmapThe same event schema accepts more than build tools — a CI pipeline, deployment job, or security scanner lands as a queryable record beside the builds it relates to.

A terminal querying the Develocity API for a build whose buildToolType is "custom", returning the same structured build record as a natively instrumented tool.

Observability

Every build tool's events land on one observability surface

Each tool's events flow into Build Scan — the build's own wide-event record, queryable end to end.
Develocity Analytics aggregates across the polyglot toolchain, so duration, failure rate, and cache coverage are comparable across projects and build tools.
The same events feed the Context Engineering Layer, giving agents the real structure of the build they reason about.

View documentation