TeamCity "Failed to resolve artifact dependency" in CI

By Daniel Zoghalchali·Latchkey

A build with an artifact dependency could not fetch the required files from its source build. Usually the source build has no matching artifact path, or no suitable source build exists for the configured revision rule.

What this error means

The build fails early with "Failed to resolve artifact dependency ..." or "No files matched the pattern" naming the source build configuration and the artifact path.

Failed to resolve artifact dependency:
No artifacts matching "dist/*.zip" found in build "Package #128" of "App / Package"

Common causes

The source build did not publish the expected artifact path

The artifact path pattern in the dependency does not match any file the source build actually published.

No suitable source build for the revision rule

The dependency's "get artifacts from" rule (last successful, same chain, or a tag) has no matching build, so there is nothing to resolve.

How to fix it

Match the artifact path to what the source publishes

1. Open the source build and check its published artifacts under the Artifacts tab.
2. Update the artifact dependency path pattern to match a real published path.
3. Re-run and confirm the dependency resolves and downloads.

# artifact dependency rule (source path => target dir)
dist/*.zip => packages

Fix the source-build selection rule

Set the dependency to pull from a source build that exists (last successful, or the same build chain via a snapshot dependency) so a matching build is available.

How to prevent it

• Keep artifact paths in dependencies aligned with what producers publish.
• Prefer same-chain artifact + snapshot dependencies so versions stay consistent.
• Verify the source build actually publishes artifacts before depending on them.

Frequently asked questions

Related guides

References

• GitHub Actions documentation