Cleanup
Images pile up with every deployment, build caches grow, and HivePaaS's records of old tasks and deployments add up. A cleanup job clears them on a schedule.
The cleanup job
Settings → Data Cleanup sets it:
| Options | What it clears |
|---|---|
| DB Cleanup Options | HivePaaS's records, once older than their retention: tasks, deployments, audit logs, system errors, deleted objects. |
| File Cleanup Options | Files HivePaaS no longer needs. |
| Cache Cleanup Options | Build caches and repository caches, past their retention. |
| Docker Swarm Cleanup Options | On every node: stopped containers, unused images, networks and volumes, and the build cache, each if chosen. |
It runs on its schedule, daily by default: a Cron Expression or an interval. Run Cleanup Now runs it at once. A notification can report each run.
By default, it keeps tasks, deployments, audit logs, system errors and deleted objects for 90 days, repository caches for 10 days, and the build cache for 30 days.
It also removes apps left behind by a project or environment that was deleted.
Prune Volumes deletes anonymous volumes no container uses. Named volumes, such as apps' storage, are kept.
Clearing caches now
Force Clear Build Cache and Force Clear Repo Cache, on the same page, clear those at once, such as when a build keeps using an outdated layer.
Backup repositories
Backup repositories are cleaned apart, by the Backup Repo Cleanup job: see Backup repositories.