Build Integration FAQ

Q: Why is the Environment tab empty?

A: Environment collection is off unless the publisher enables it. A successful Maven or Gradle publish can still show 0 Environment Variables and 0 System Variables. Enable includeEnvVars or the equivalent JFrog CLI collection if you need that data, and keep secret-exclusion patterns.

Q: Why does Maven print Skipping artifact deployment on success?

A: The Maven Artifactory Plugin replaces Maven's default deployer. Maven reports that its own deploy is skipped. The plugin then uploads artifacts and build-info. Look for Deploying artifact and Build-info successfully deployed after that line.

Q: Why did GitHub jf rt ping return 401 after it worked locally?

A: A GitHub secret can hold an expired access token while your laptop CLI still refreshes a token. Rotate JF_ACCESS_TOKEN or use OpenID Connect (OIDC) so each run gets a short-lived token. Store JF_URL as a variable, not a secret.

Q: Why does build-info show two identical VCS entries?

A: You collected Git metadata twice. Do not run jf rt bag and also rely on the Setup JFrog CLI action's automatic post-step Git collection. Use the full manual sequence bce + bag + bp, or leave metadata and publication to the action.

Q: Why is my build missing from Artifactory > Builds?

A: Confirm publication completed, the build name and number match the job, and the JFrog project context matches. Also confirm permission to read build-info. Generic uploads to a non-existent or wrong-type repository can fail before publication, for example HTTP 405.

Q: Why do artifacts exist when there is no build?

A: The upload or deploy ran without a build-info publish step, or auto-publish was disabled and jf rt bp or build-publish did not run. Associate the same build name and number, then publish.

Q: What should I do if I already have the Jenkins Artifactory Plugin, Bamboo Artifactory Plugin, or TeamCity Artifactory Plugin?

A: Keep that job running, then migrate. Do not start a new job from those pages. Use Legacy Plugins for the replacement table: Jenkins JFrog Plugin, JFrog CLI in Bamboo or TeamCity, or the current Azure DevOps extension for old VSTS tasks.

Q: Should I use a plugin or JFrog CLI?

A: If Maven or Gradle should own publisher configuration, use the Artifactory plugin for that tool. If CI standardizes on jf, or the package type has no plugin page in this tree, use JFrog CLI. Hosted CI should start with the current wrapper. For more information, see Choose Plugin, CLI, or CI Wrapper.

Q: Is build promotion the same as Release Lifecycle Management?

A: No. Manage Builds documents Artifactory build promotion, which copies or moves artifacts for a build. Release Lifecycle Management is a separate product path. Use promotion when you need repository promotion of a published build.