While reviewing what is needed to migrate Archiva to Buster, I noticed the following:
elukey@archiva1001:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/vdb1 98G 85G 8.4G 92% /var/lib/archiva
elukey@archiva1001:/var/lib/archiva/repositories$ sudo du -hs * 68K internal 16G mirrored 665M python 34G releases 34G snapshots elukey@archiva1001:/var/lib/archiva/repositories$ sudo du -hs * releases/ 68K internal 16G mirrored 665M python 34G releases 34G snapshots elukey@archiva1001:/var/lib/archiva/repositories$ sudo du -hs * snapshots/ 68K internal 16G mirrored 665M python 34G releases 34G snapshots
Config for Releases:
Config for Snapshots:
Given something like the timestamp below, the config is not really purging anything:
elukey@archiva1001:/var/lib/archiva/repositories/snapshots$ ls -ld ./org/wikimedia/analytics/refinery/job/refinery-job/0.0.14-SNAPSHOT drwxr-xr-x 2 archiva archiva 4096 Jun 18 2015 ./org/wikimedia/analytics/refinery/job/refinery-job/0.0.14-SNAPSHOT
https://archiva.apache.org/docs/2.2.4/adminguide/repositories.html
I have limited understanding of Archiva but what I'd do is something like the following:
- set retention days to 0 to disable it (and rely only on the option below)
- set retention count to something like 3/5
- test enabling the "delete released snapshot" button to see if any clean up is triggered
Thoughts?