Browse documentation

Administration

Retention policies

Keep the newest matching versions and let Blob Yard remove the rest.

Before you start

  • Select the exact workspace and project before changing retention.
  • Use a plan that includes retention policies.

Apply explicit retention

retention commands
blobyard retention set --latest 20 --branch main --path 'releases/**' blobyard retention show blobyard retention clear

A retention policy keeps the newest matching versions. It only removes versions that match its project, path, and optional branch scope. Share or grant expiry does not invoke retention. Commands act on the workspace and project stored by blobyard init, or explicit --workspace and --project flags.

Write safe policy rules

  • --latest takes a positive whole number of versions to keep.
  • Globs support * and ** and can be up to 256 characters.
  • Path globs match remote logical paths and cannot start with / or contain .. segments.
  • Branch globs match explicit git branch provenance recorded at upload time.

Know the plan requirement

Retention is included in the Team and BYO Storage plans. Every run records how many versions were considered and deleted, and the project settings page shows the last run.

Reference and troubleshooting

Syntax and behavior

Reusable syntax

retention syntax
blobyard --workspace <workspace-slug> --project <project-slug> retention set --latest <count> [--branch <glob>] [--path <glob>]

Concrete example

release retention policy
blobyard --workspace demo-team --project release-files retention set --latest 20 --branch main --path 'releases/**'

Values used

--latest 20
Keeps the newest twenty versions matching the remaining filters.
--branch main
Matches explicit main-branch provenance only.
--path 'releases/**'
Matches remote logical paths, not local filesystem paths.
demo-team and release-files
Remote workspace and project scope whose versions may be removed.

Expected result

The active project policy is replaced and future runs keep only the newest matching versions.

If it fails

  • Run retention show with the same scope to inspect the current policy.
  • Shorten a glob that exceeds 256 characters or remove unsafe characters.

Security and lifecycle

Retention can permanently remove old matching versions. Review scope before saving.