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

RE: post-commit export

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Wed, 17 Jun 2009 14:45:26 +0100

> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2009b_at_ryandesign.com]
> Sent: Wednesday, June 17, 2009 8:09 AM
> To: Justus Stadler_external
> Cc: users_at_subversion.tigris.org
> Subject: Re: post-commit export

> > Andrew sent(send?!? In other words: I have it already;-) ) me his
> > script,
> > which only needs a little rewriting, as he wrote. I'll give it a
> shot.
> And the script tries to emulate "svn up" for an export as opposed to
> a working copy, yes? If it works for you, great! But you're still
> going to end up with about 450GB of space taken up with these
> exports, right?

Yup, it actually writes a file of changed dirs to a file, then a nightly
script takes then, exports the directories, runs doxygen on them, then
deletes the directories. Remove the doxygen+deletion and you have the
equivalent of 'svn up' that uses export.

I understand where he's coming from, if you have a 500Gb drive, then
buying a new one and raiding it to appear as a 1TB partition can cost...
and then someone adds another 100Gb project and you need to explain why
you have to buy a third drive, and a raid controller and an enclosure to
put them in :)

At my company, getting signoff to buy a 10Gb drive is too much hassle
(unless it goes on expenses ;) )


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-17 15:46:33 CEST

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