We currently store tarballs of our system in artifactory after each build. We
do not use maven, gradle, etc., so we store them in a generic repository.

The problem that we are having is that the repository keeps growing and
growing because each build is a separate artifact; however, old versions of
the build are not really useful.

For maven/gradle repositories, we could configure the repository as a
snapshot repository and limit versions to a small number.

Is there some way to limit the number of artifacts in a generic repository
in a similar manner? For example, only allow 5 artifacts (our build
tarballs) in the repository. If you put in more than five, the oldest
artifact will be deleted.

Thanks.

David




--
View this message in context: 
http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to