Hey! These docs are for version 1.0, which is no longer officially supported. Click here for the latest version, 1.2!

Retention / Lifecycle

Enabling and Configuring Retention / Lifecycle policies

Automated retention/lifetime rules (available on the Velocity plan and above) allow you to automatically manage storage for packages by deleting or moving packages that fall outside of the defined retention rules. Assets can be expired based on the number of packages (count), size of packages (bytes), or by the number of days (time).

To enable and configure retention/lifecycle rules, click "Retention Rules" in the lefthand menu on a repository detail page, then use the sliders to set your policy and finally click the green "Enable Lifecycle" button.

Enabling Retention / Lifecycle policyEnabling Retention / Lifecycle policy

Enabling Retention / Lifecycle policy

Example - Retention Policy that deletes packages older than 90 days

To configure a retention / lifecycle policy that removes packages older than 90 days, you would set the following:

  • "Limit By Days" = 90
  • "Limit By Count" = 0 (disabled)
  • "Limit By Size" = 0.0B (disabled)

By disabling count and size, it means it only uses the package age to delete

90 day Retention Policy90 day Retention Policy

90 day Retention Policy

The retention rules are disjunctive, so it uses all three to select what to delete.
If grouping is selected, it applies to the rules to each "grouping". Otherwise, it's across all packages within a repository.


Retention rules only activate when packages are uploaded (synchronised). So you could have one package at 1000 days, and the 90 days retention still wouldn't activate. Only after uploading a new package would the 1000 day package be deleted.

Did this page help you?