We have an Archiva server (running version 1.1.3) that is out of disk space. It has two managed repositories, "internal" and "snapshots".
The "internal" repository is a Maven 2.x repository, with Purge By Days Older Than = 30, Purge By Retention Count = 2. Releases Included is checked, Snapshots Included is unchecked, Scannable is checked, Delete Released Snapshots is unchecked. The cron for this repository is "0 0 * * * ?". The "snapshots" repository is a Maven 2.x repository, with Purge By Days Older Than = 3, Purge By Retention Count = 3. Releases Included is unchecked, Snapshots Included is checked, Scannable is checked, Delete Released Snapshots is unchecked. The cron for this repository is "0 0,30 * * * ?". There are only two users defined, "admin" (which has the System Administrator role) and "guest" (which has Global Repository Manager and Local Repository Manager roles). As far as I can tell, the builds that are uploading artifacts to this repository are doing so essentially anonymously. All of the files in the Archiva repository file tree are owned by root. I am unable to get a "Delete Artifact" button in the web GUI for any artifact at all. It appears that my only way of cleaning up disk space on this server would be to delete files from the tree via the command line. I would like to find a better way to delete (and also manage) the older artifacts in these repositories. I'm very new at this, so any and all help is welcome. Thanks in advance. David Rosenfeld Build Engineer WDPRO Development Services
