[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: How to prune old versions of an artefact?

From: David Aldrich <David.Aldrich_at_EMEA.NEC.COM>
Date: Mon, 15 Jul 2013 09:58:38 +0000

Hi Mark

> For your uses, perhaps you could spin this artifact off into it's own repository
> (use "external"s from your main repo if required) and then you can archive
> that repo off whenever necessary?

That's a great idea,

Thanks

David

> -----Original Message-----
> From: Cooke, Mark [mailto:mark.cooke_at_siemens.com]
> Sent: 15 July 2013 10:50
> To: David Aldrich; 'users_at_subversion.apache.org'
> (users_at_subversion.apache.org)
> Subject: RE: How to prune old versions of an artefact?
>
> > -----Original Message-----
> > From: David Aldrich [mailto:David.Aldrich_at_EMEA.NEC.COM]
> > Sent: 15 July 2013 10:09
> > To: 'users_at_subversion.apache.org' (users_at_subversion.apache.org)
> > Subject: How to prune old versions of an artefact?
> >
> > Hi
> >
> > We are running a svn 1.7 server.
> >
> > One of our repositories contains an artefact that is 4GB. It consists
> > of a set of regression test results that we want to version control.
> > This artefact changes infrequently - say every month or two - but it's
> > enormous size is causing concern for IT Manager, as the svn database
> > is slowly increasing in size.
> >
> > I would like to prune very old versions of this artefact from the
> > server's database. I realise that pruning is not generally a good
> > idea for a version control system, but this is an exceptional case.
> >
> > What is the current status of pruning in svn, i.e. how can I do it?
>
> This seems to be called "obliterate" in subversion and is one of the "most
> wanted" features in the roadmap [1] but is currently slated for "2.0?" A web
> search for "subversion obliterate" will help you find the gory details.
>
> [1] http://subversion.apache.org/roadmap.html
>
> I believe that the only way you can currently remove items is through careful
> use of svn dump / filter / load with the sides effect of probably requiring all
> users to check out new working copies.
>
> For your uses, perhaps you could spin this artifact off into it's own repository
> (use "external"s from your main repo if required) and then you can archive
> that repo off whenever necessary?
>
> ~ Mark C
>
> > Best regards
> >
> > David
> >
>
> Click
> https://www.mailcontrol.com/sr/TfcnIiq+PCrGX2PQPOmvUpFBc4ZD8M8UYq
> XdQke3IG8VxJBrTnjnEEpfbe+cKMM7x7UZkiVaIJf5pl0FDW8fzw== to report
> this email as spam.
Received on 2013-07-15 11:59:21 CEST

This is an archived mail posted to the Subversion Users mailing list.