We are using Nexus to deploy our snapshot artifacts. Our build server deploys them during each build using the following command: mvn deploy. As result on each build the new
Create a scheduled task to purge out old snapshots.
The following links describe the functionality:
You can configure the task to always keep a minimum number of artifacts. It's very flexible.
The only "gotcha" in Version 2 of the Repository Manager, is that you'll need to also run a second task, Empty Trash, in order to claim back the disk space. For Version 3 you will need to run Compact blob store to ensure that the deletion will return the disk space. See docs above.
I suspect not. http://weblogs.java.net/blog/johnsmart/archive/2010/01/03/tale-two-repository-managers-nexus-and-artifactory-compared-and-co
Artifactory [...] also lets you limit the number of snapshots per artifact for each repository.
This is said in contradiction to Nexus.
With Nexus OSS 3.x there are:
and each task has:
If you have the administrator access in Nexus Then,
Login to Nexus.
Browse to Administration.
Go to scheduled Tasks.
You can add the task : Remove Old Snapshots.
Select task type as Remove Snapshots from repository.
You can define Minimum Snapshot count or Snapshot retention as needed.