ARTIFACTORY: How to Restore the Missing 'Cleanup' Button for Received Release Bundles v1

Products
Frog_Artifactory
Content Type
Use_Case
AuthorFullName__c
Zhang Hailang
articleNumber
000007078
FirstPublishedDate
2026-07-21T11:48:56Z
lastModifiedDate
2026-07-21

ARTIFACTORY: How to Restore the Missing 'Cleanup' Button for Received Release Bundles v1

Introduction
When managing Received Release Bundles v1, users may notice that the ‘Cleanup’ option is not available in the JFrog Platform UI.
This occurs when the Release Bundle Retention feature is disabled. When retention is disabled, the Cleanup functionality is hidden from the UI even if the user has administrator permissions.
This article explains how to verify and enable the Release Bundle Retention configuration using the Artifactory REST API.


Issue Description
When viewing a received Release Bundle v1 in the JFrog Platform UI, the Cleanup option is missing.
Expected behavior: The Cleanup option should be available after Release Bundle Retention is enabled.


Root Cause
The Cleanup functionality for received Release Bundle v1 depends on the Release Bundle Retention configuration. When Release Bundle Retention is disabled:
{ "enable": false }
Artifactory does not display the Cleanup option.


Resolution
1. Verify Release Bundle Retention status
Run:
curl --request GET \
     --url https://<ARTIFACTORY_URL>/artifactory/api/v1/bundle/retention/config/enable \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <TOKEN>'
The API request requires an administrator-level user.
Example response:
{
  "enable": false
}


2. Enable Release Bundle Retention
If the response shows "enable": false, enable the retention configuration using the following API:
Run:
curl --request POST \
     --url https://<ARTIFACTORY_URL>/artifactory/api/v1/bundle/retention/config/enable \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <TOKEN>' \
     --header 'content-type: application/json' \
     --data '{"enable":true}'
Expected response:
{
  "enable": true
}


3. Verify UI