This topic outlines the limitations of the Cleanup solution.
Current Limitations of Cleanup Policies - Packages
Supported Repositories
Supports Local and Federated repositories. Does not support Remote and Virtual repositories.
Note
When cleaning Federated repositories, the run (dry or actual) can take significantly longer compared to Local repositories. This is because the cleanup workflow must check the last download status of each package across all federation members. The more members involved, the longer the process will take.
Recommendations to Optimize Cleanup:
Adjust Policy Conditions: Narrow the scope of your cleanup policies to reduce the number of packages to be deleted in each run. This can significantly speed up the run.
Increase Run Frequency: Run cleanup policies more often to process smaller sets of packages. This helps prevent large backlogs and improves long-term performance.
Package Verification
There is no verification if packages are part of a Release Bundle or build. A package-level Cleanup policy may impact build or release bundle promotion.
Cleanup Limits
Cleanup policy can delete up to 100,000 packages in a single run.
Progress Notifications
Notifications on the progress of a cleanup policy run are unavailable.
Visibility of Run Results
Run results for global policies are visible only to Platform admins globally.
Cleanup Policy
The Cleanup policy does not execute when an ongoing mandatory task is in progress (for example, Garbage Collection).
Search Policies
A project admin can only perform searches within their project context and does not have access to the global scope.
Artifactory Configuration
Artifactory Instance can only be a Platform or a Mothership, not an Edge
Concurrent Execution and Queuing of Cleanup Policies
Cleanup Policies can run concurrently up to a specified maximum. When this limit is reached, additional triggered policies are queued. Any further triggered policies will be skipped entirely if the queue reaches its maximum capacity.
In the current version of Artifactory, queued or skipped policy runs do not appear in the Runs view. You can find a log of skipped policies in the Artifactory Service log. For example, you might see a message like:
"Policy: test_policy run: 1 has been rejected since allowed 3 concurrent runs are already in progress."
Current Limitations of Cleanup Policies - Release Bundle V2
Distributed Release Bundles
Cleanup policies will not delete distributed release bundles.
Source Artifacts
The source of release bundles, including associated builds and artifacts, will not be deleted.