Inspect Builds

Inspect Builds is the JFrog Artifactory UI workflow for reading a published build-info record. Use it after the first successful publish to confirm modules, artifacts, and optional version control system (VCS) or environment data.

Why Inspection Matters

You use inspection to prove the integration produced one identity of name and number and attached the expected modules. Do this before Manage Builds operations.

Before You Begin

Publish build-info from a supported build integration.
Know the build name and, for a specific run, the build number.
Make sure your account can read the relevant build and repository content.

Find the Build

To find the build:

In the JFrog Platform, go to Artifactory > Builds.
Find the row by Build Name. Note Last Build Number, Published Modules, Project, and Build Repository.
Open the build name, then select a build number.

If the build is not listed:

To check why a build is not listed:

Confirm that the publisher completed its build-info publication step.
Check that the build name and project context match the publishing job.
Confirm that your account has access to the repositories associated with the build.

Inspect a Build Run

Use the tabs on the build number. Typical labels include Published Modules, Environment, Xray Data, Evidence, Issues, Diff, Release History, VCS, and Build Info JSON. The following table maps inspection questions to the fields and tabs on the build run.

Question	Where to Look
When and where did it run?	Header fields: start time, duration, build tool, CI, build URL
What did it produce?	Published Modules: module id, artifact count, checksum columns
What did it consume?	Module dependency lists and scopes
Which source produced it?	VCS when the publisher collected Git metadata
Which work items relate to it?	Issues when collected
Which properties describe the run?	Environment: Environment Variables and System Variables

Expected empty Environment. If collection was not enabled, you see 0 Environment Variables and 0 System Variables. That doesn't mean publication failed. For more information, see Build Integration FAQ.

The details you see for a build depend on the data collected by its publishing integration and on the services enabled for the JFrog Platform deployment.

Next Steps

To append another published build, promote outputs, or set retention, see Manage Builds.
To understand the record itself, see About Build Info.
To understand storage and access implications, see Build-Info Repository.

Troubleshooting

The following table lists common inspection symptoms and what to check.

Symptom	Likely Cause	What to Check
Build name is absent	Build-info was not published, or project context differs	Publisher completion, build name, and project key
A module has no expected artifacts	The package step did not associate outputs with this build identity	Integration configuration and matching build name/number
Dependencies or VCS data are absent	That data was not collected by the publishing path	Package extractor and source-collection settings
Duplicate VCS entries	Two collectors ran in the same job	Build Integration FAQ
A detail view is absent	No corresponding data exists, or the feature is unavailable	Collected record, permissions, edition, and enabled services