About Build Info

Build-info is the metadata record that identifies a run by build name and build number and lists the modules, artifacts, and dependencies that belong to that run. This topic distinguishes the record from repository files and describes the Builds UI in JFrog Artifactory.

Artifacts answer what was stored. Build-info answers which job produced it. Inspection, promotion, and retention operate on the record, not on a folder listing alone.

Why It Matters

A published record lets you list CI runs, compare modules, and promote by build identity. Browsing repositories alone doesn't provide that identity. Permissions for deploy, read, and delete build-info are separate from ordinary artifact deploy.

When to Read This Page

You can return to this topic after you pick an integration on Build Integration, or when a UI tab is empty and you need to know whether that is expected.

What the Record Contains

A build-info record can include:

Build and CI tool names and versions
Start time and duration
Modules produced by the build, including artifact counts, checksums, and paths
Resolved dependencies and scopes
Optional properties, version control system (VCS) details, and related issues
Optional environment properties and Java Virtual Machine (JVM) system properties

A JFrog project key can scope which builds appear in the list you are viewing. A mismatch looks like a missing publish.

Environment collection is off by default on typical Maven plugin jobs and on CLI flows. An empty Environment tab with 0 Environment Variables and 0 System Variables still means a successful publish.

How Build-Info Reaches Artifactory

A package extractor, JFrog CLI, or CI wrapper collects metadata during the job, associates it with one name and number, and publishes through the Artifactory build API. The default repository association is artifactory-build-info. For more information, see How Build Integration Works.

JFrog provides collection paths for Gradle, Ivy, Maven, npm, Go, pip, NuGet, and Docker. Maven and Gradle have dedicated plugin pages. For more information, see Maven Artifactory Plugin and Artifactory Gradle Plugin. Other types use JFrog CLI. For more information, see JFrog Build Offerings by Package Type.

What You Can Inspect in the UI

Published records appear under Artifactory > Builds. The list shows columns such as Build Name, Last Build Number, Published Modules, Last Build Time, Project, and Build Repository. The typical repository key is artifactory-build-info.

A build number includes tabs such as Published Modules, Environment, Xray Data, Evidence, Issues, Diff, Release History, VCS, and Build Info JSON. Published Modules lists module ID, artifact count, and artifact and dependency checksum columns when those columns are present.

The record can answer:

Which modules and artifacts did this build produce?
Which dependencies did each module consume?
Which build tool and CI agent ran the build?
Which source revision or tracked issues relate to the build?
How does this run differ from another run?

For more information, see Inspect Builds.

Troubleshooting

The following symptoms are common when a publish is missing or incomplete.

Symptom	Likely Cause	What to Check
The build can't be found	The name, number, or project context differs from the publishing job	The published identity may not match the identity you are inspecting
Artifacts appear but build context doesn't	The artifact operation and build-info publication weren't completed as one workflow	The selected integration's publication step may be incomplete
The Environment tab is empty	Environment collection is off unless the publisher enables it	Collection is needed only when environment data is required, and secret-exclusion patterns still apply