Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >


As customers adopt and scale with JFrog Distribution and Artifactory Edges, managing the lifecycle and number of Release Bundles has become challenging. To help admins manage Release Bundles and to clean up older items, JFrog has created an automated cleanup process for received Release Bundles, which enables deleting target Release Bundles that were distributed to a specific Artifactory Edge instance. These retention policies are set up using Artifactory REST APIs, and can be customized as needed. 

In addition to automated retention and cleanup using REST APIs, JFrog also developed a new UI functionality that enables you to manage these Release Bundles in the JFrog Platform. See Managing Release Bundles in the JFrog Platform UI.

The Release Bundle retention policies also enable you to configure a policy to keep a Release Bundle (i.e., keep the Release Bundle indefinitely, which prevents it from being deleted), not to keep it (set the item to Don’t Keep so that it is eligible for deletion), and to delete Release Bundles received by the Artifactory Edge. 

The implementation of this feature provides the following enhancements:

  • Saves storage
  • Removes redundant releases
  • Enable distribution of releases that holds different artifacts under the same path. (e.g., Docker pages with latest tags) 
  • Security - makes sure that distributed artifacts are certified again (by requiring redistribution of old bundles


Setting retention policies, and using the Cleanup Report (and Cleanup History function) require an admin-level user. In addition, the functionality must be enabled by setting the Set Retention Policies to Enabled REST API to true.

JFrog Subscription Levels

Page contents

Release Bundle Retention Policies

Policies are defined using the Artifactory REST APIs.

Automatic Deletion

The retention policy enables you to set auto deletion for Release Bundles from Artifactory Edges. This policy looks for Release Bundles that meet both of the following criteria, and then automatically deletes the Release Bundles when the cleanup process runs. A Release Bundle version is automatically marked and deleted when it meets both of the following criteria:

  • The maximum number of versions allowed for this Release Bundle has been reached
  • The Release Bundle version release date is older than the maximum number of days allowed for a released version

If a release bundle does not meet both of these criteria, it will not be deleted automatically (but can be deleted manually).

This is configured using the REST APIs - see Get Retention Policy Configuration for details.

Reports for Manual Deletion

There are two parameters for the retention policy that are relevant to manual deletion of a Release Bundle. If a Release Bundle meets one or both the parameters you set, this will make the Release Bundle a candidate for deletion, meaning it will appear in the report.: 

  • Limit the number of versions per Release Bundles - Define the number of versions to keep for the Release Bundle. 
  • Release Bundle version release date - Define the maximum number of days to keep a released version. 

You can define more than one policy; when defining more than one policy, if a Release Bundle meets one or more of the policies it will be marked for retention/deletion.

Note that the retention policy will always be a combination of the two settings (the number of versions and the number of days). If you change only one of these values, the other one will remain the default (the last defined value).

To learn more, see the Retention Policy REST API.

Next: Managing Release Bundles in the JFrog Platform UI.

  • No labels
Copyright © 2023 JFrog Ltd.