Nexus Repo cleanup policy
This section explains the SHIP-HATS cleanup policy for your Nexus repositories and provides recommendations to help you maintain performance and storage efficiency.
Why do we need a cleanup policy?
A cleanup policy automatically removes unused components (artefacts) to:
Optimise storage utilisation
Improve repository performance
Maintain repository health and manageability
SHIP-HATS uses Nexus Cleanup Policies to manage components at the repository level.
SHIP-HATS default cleanup policy
Our default cleanup policy is configured to automatically delete a component from your Nexus repository after 180 days from the date of its creation.
Things to note
The cleanup policy applies at the repository level, not at the subscription or billing account level.
The cleanup task runs daily at 01:00 AM.
Deleted components cannot be recovered by SHIP-HATS.
If your repository is large (>10 GB) and you frequently upload large artefacts, Contact us to change your cleanup policy to 90/60/30 days.
We strongly recommend you to periodically review your repositories and to maintain them proactively.
- Back up and store the artefacts in your own S3 bucket/storage services if needed.
- If you require a clean up policy greater than 180 days for your repo, Contact us. The SHIP-HATS team will assess the repo and advise you accordingly.
30/60/90 Days cleanup policy criteria
For repositories with high storage usage, SHIP-HATS can configure stricter cleanup policies. Components are eligible for deletion when both conditions below are met:
The component was created more than 30 / 60 / 90 days ago, and
The component has not been downloaded within the same period.
If either condition is not met, the component will not be deleted. The cleanup policy primarily uses the component creation date as the reference point.
Recommendations
We strongly recommend that you actively manage your repositories:
Back up critical artefacts to your own storage (e.g., S3 or other storage services)
Regularly review repositories and remove obsolete components
Avoid relying on Nexus as long-term archival storage
If you require a cleanup policy longer than 180 days, Contact us. The SHIP-HATS team will review your repository and advise accordingly.
