Build Integration Glossary
Look up JFrog Artifactory build-info terms used in Build Integration.
This glossary defines terms used across Build Integration topics. For the overall model, see How Build Integration Works. The following table lists each term and its definition.
| Term | Definition | See Also |
|---|---|---|
| Artifact | An artifact is a file stored in a JFrog Artifactory repository, for example a JAR, POM, or generic file. Artifacts are outputs. They are not the build-info record. | About Build Info |
artifactory-build-info | artifactory-build-info is the default repository associated with published build-info records. It appears as Build Repository on the Builds list. | Build-Info Repository |
| Build name | A build name is the human-readable identity for a stream of runs. The default often comes from the project, workflow, or Jenkins job name. | Inspect Builds |
| Build number | A build number is the identity of a single run under a build name. It may be a CI run number or an epoch timestamp. | Inspect Builds |
| Build-info | Build-info is a metadata record that ties a build name and number to modules, artifacts, dependencies, and optional environment, version control system or VCS, and issues. | About Build Info |
| CI wrapper | A CI wrapper is a CI-specific integration that installs or exposes JFrog CLI or plugin steps and usually injects credentials and build identity. | Choose Plugin, CLI, or CI Wrapper |
| Config Token | A Config Token is the output of jf config export for a configured JFrog server. Some pipes use it, and it is a secret. | JFrog Setup CLI Bitbucket Pipe |
deploy (Maven) | The Maven deploy lifecycle phase publishes to a remote repository. You use it when the goal is Artifactory deployment. The install phase only writes to the local Maven cache. | Maven Artifactory Plugin |
| Environment collection | Environment collection is the optional capture of process environment and JVM and system properties into build-info. It is off unless enabled. Secret-shaped keys should be excluded. | About Build Info |
| Environment Variables / System Variables | Environment Variables and System Variables are labels on the build Environment tab in the JFrog Platform UI. | Inspect Builds |
| Module | A module is a unit inside build-info, typically one Maven or Gradle coordinate or CLI module identifier, with artifact and dependency counts. | Inspect Builds |
| OIDC | OIDC is short-lived authentication from the CI platform to JFrog using an identity mapping, instead of a long-lived access token. | GitHub Actions |
| Project key | A project key is a JFrog Project identifier that can scope builds. A mismatch hides builds from the list you are viewing. | Inspect Builds |
| Promotion | Promotion is the copy or move of a build's artifacts to a target repository, with optional status and properties. Promotion is distinct from Release Lifecycle Management. | Manage Builds |
| Publication (Gradle) | A Gradle publication is a Gradle maven-publish or ivy-publish publication that the Artifactory plugin deploys. | Artifactory Gradle Plugin |
| Retention / discard | Retention or discard is the removal of old build-info runs by age or count. Artifact deletion is a separate, broader option. | Manage Builds |
| Access token | An access token is a JFrog identity used by JFrog CLI and many CI secrets (JF_ACCESS_TOKEN). It can expire even when a local CLI session still refreshes. | Build Integration FAQ |
Related Topics
Updated about 1 hour ago
Did this page help you?
