Build-Info Repository
Understand how the Artifactory build-info repository affects publication, access, and retention.
The Build-Info Repository is the JFrog Artifactory store associated with published build-info records. As an administrator or release engineer, you can keep publication, inspection, and cleanup from treating build history as ordinary artifacts.
Why Administrators Care
Every successful Build Integration job writes a record that the Builds UI lists under Build Repository artifactory-build-info. If that repository is cleaned, replicated, or permission-locked like a generic file repository, publishers fail, readers lose history, and retention can delete more than intended.
Artifactory uses artifactory-build-info as the default repository associated with published build-info. Clients publish through the build API. They do not treat this key as a package-type local for JARs or Docker images.
What This Repository Supports
JFrog clients publish a completed build-info record through Artifactory's build API. Other build operations retrieve build records and runs, append published builds, promote build outputs, or apply retention.
These operations can require permissions associated with build-info:
- Publication requires permission to deploy build-info.
- Appending a published build requires permission to read its build-info.
- Discarding builds requires permission to delete build-info.
- Deleting associated artifacts is a separate, broader scope.
For the fields contained in a record, see About Build Info.
Build-Info as Managed System Data
Build-info provides the provenance used by build inspection and management workflows. Before applying repository cleanup, retention, replication, or permission changes:
- Identify any rule that can include
artifactory-build-info. - Confirm whether the rule targets only build records or also associated artifacts.
- Verify that publishers retain deploy permission and readers retain the access required by their tasks.
- Validate the change in a non-production environment or with a non-destructive preview when available.
Do not treat this repository as an ordinary artifact destination without confirming the effect on build history.
Troubleshooting
The following table lists common symptoms, their likely causes, and what to check.
| Symptom | Likely cause | What to check |
|---|---|---|
| Build publication is denied | The publisher lacks build-info deploy permission | Account, project context, and repository permissions |
| An aggregate cannot append a build | The source record is absent or unreadable | Source build name and number, publication, project, and read permission |
| Build history disappears unexpectedly | Retention or cleanup included build-info | Recent retention, cleanup, permission, and administrative changes |
| Artifact files were removed with build retention | Artifact deletion was enabled | Retention options and operation audit trail |
Related Topics
Updated about 1 month ago