Skip to content
Latchkey

Bamboo "shared artifact not found" (subscription) in CI

A downstream job subscribed to a shared artifact from an upstream job in the same plan, but Bamboo found no such shared artifact to transfer. The upstream artifact is not shared, was not produced, or the subscription is misnamed.

What this error means

A dependent job fails with "shared artifact <name> not found" or "Could not find the shared artifact", so the files it expected are missing.

Bamboo
The shared artifact 'app-jar' could not be found.
Ensure the producing job defines it as a shared artifact and that the job succeeded.

Common causes

The upstream artifact is not marked shared

The producing job defines the artifact but not as a shared artifact, so downstream jobs in the plan cannot subscribe to it.

The upstream job did not run or failed

The job that should publish the artifact was skipped or failed, so there is nothing to transfer to the subscriber.

How to fix it

Mark the artifact shared and subscribe correctly

  1. In the producing job, edit the artifact definition and enable "Shared".
  2. In the consuming job, add an artifact subscription to that shared artifact by the same name.
  3. Ensure job ordering so the producer runs before the subscriber.
Bamboo administration
# Producing job > Artifacts > <definition> > Shared: Yes
# Consuming job > Artifact subscriptions > add subscription to <definition>

Guarantee the producer succeeds first

Order the jobs so the artifact producer completes successfully before any subscriber runs.

How to prevent it

  • Mark artifacts shared the moment another job needs them.
  • Keep subscription names identical to the producing artifact definition.
  • Order plan jobs so producers precede subscribers.

Related guides

Run this faster and cheaper on Latchkey managed runners. Start free →