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

Re: SVN as CMS

From: David Weintraub <qazwart_at_gmail.com>
Date: Fri, 20 Mar 2009 14:12:21 -0400

It might be easier for a QA organization to pull off the needed
binaries off an actual "Release Repository" rather than using
Subversion for this task. Non-programmers may find pulling what they
need off of a release repository easier than doing a checkout in
Subversion.

If you use a Release repository, it's pretty easy to delete the older
obsolete versions of files. The advantage is that there's no way
someone can use an obsolete version of an object once it is no longer
in the

Another problem is that Subversion does not provides an easy way to
delete older obsolete binaries, so the size of the repository can
build up rather quickly. If you do use Subversion for this type of
job, you may want a different Subversion repository for storing
release items. This will allow you to remove obsolete releases via the
svnadmin dump/load command without taking down your source repository
itself.

We use Nexus (a Maven Repository) for all of our releases and
dependent jars that one project will build, but other projects will
need. It wasn't easy to get it to work, but we found we can fetch
items via the Ant <get> task, and put items into our repository by
using some shell scripting and the Maven "deploy:deploy-file" mojo.

On Fri, Mar 20, 2009 at 12:49 PM, Bolstridge, Andrew
<andy.bolstridge_at_intergraph.com> wrote:
> Not storing temporaries is an obvious 'best practice' for any SCM, but
> there is often a requirement to store the built objects - eg the exes,
> dlls or other binary targets.
>
> If you do store binaries in SVN, then you can get them out easily
> without re-building them. Often a implementation, project or QA person
> will not have the skills or setup required to re-build, so needs to have
> the binaries pre-built. If they're stored in SVN, then they can also get
> the correct version without worrying that what they get to re-build will
> be what was originally shipped.
>
> We store all shippable binaries in SVN, and use svn:externals to help
> ease fetching them from the repository.
>
> Andy
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1365778
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>

-- 
--
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1366368
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-20 19:13:36 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.