Artifactory storage quota exceeded on upload in CI

Artifactory enforces a storage quota. When usage crosses the configured limit, it refuses new uploads and logs a quota message. Publishes fail until space is freed or the quota is raised.

What this error means

Deploys start failing across jobs at once, with an Artifactory error that the storage quota limit has been exceeded and uploads are blocked. Reads still work.

Artifactory

Received status code 403 from server: Datastore disk quota was exceeded.
Storage quota limit reached: usage 95% of the configured limit. Blocking further deployments.

Common causes

The instance crossed its configured storage quota

Total artifact storage passed the quota limit set in Admin, so Artifactory blocks deployments to protect the datastore.

No retention policy on snapshot/CI repos

CI produces many transient artifacts; without cleanup or max-unique-snapshots limits, storage fills over time.

How to fix it

Free space or raise the quota

In Admin, review the storage quota and current usage.
Delete old snapshots/build artifacts or run garbage collection to reclaim space.
Raise the quota limit if the disk genuinely has headroom.

Add retention to CI repositories

Cap unique snapshots and set a cleanup policy so transient CI artifacts do not accumulate.

Terminal

# Set "Max Unique Snapshots" on the snapshot repo,
# or delete artifacts older than N days via AQL / the Cleanup plugin.

How to prevent it

Set a retention/cleanup policy on CI and snapshot repositories.
Alert on storage usage before it reaches the quota.
Run periodic garbage collection to reclaim unreferenced binaries.