Artifactory "build info not found" in CI

A jf operation looked up build info by name and number and found none. The build was never published, or the name/number does not match what was published.

What this error means

A jf rt build-promote, jf build-scan, or jf rt download --build step fails with "Build ... not found" or "No build was found for build name and number".

[Error] Artifactory response: 404 Not Found
No build was found for build name 'my-build' and number '11'.

Common causes

The build was never published

A downstream step consumes build info that jf rt build-publish never ran for, so the lookup returns 404.

A mismatched build name or number

The consuming step uses a different name or number than the publish step, so it looks up a build that does not exist.

How to fix it

Publish before consuming the build

1. Ensure jf rt build-publish runs before promote, scan, or build download.
2. Use identical name and number across publish and consume steps.
3. Re-run so the consuming step finds the published build.

jf rt build-publish my-build ${{ github.run_number }}
jf rt build-promote my-build ${{ github.run_number }} libs-release-local

List builds to confirm the name and number

Query Artifactory for the published builds to verify the exact name and number the downstream step should use.

jf rt curl -XGET "/api/build/my-build"

How to prevent it

• Publish build info before any step that consumes it.
• Share the build name and number via env vars across jobs.
• Derive the number from the CI run to keep it consistent.

Related guides