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

Re: Best practice for tagging built artefacts

From: Reinhard Brandstädter <reinhard.brandstaedter_at_jku.at>
Date: 2006-10-31 14:29:56 CET

I would suggest another solution:

create another directory on the same level as /trunk and /tags
called /artefacts or /archives and everytime you tag a build
(eg. /tags/myfancysoftware-1.2.3/ src....) you place the artefacts in the
artefacts directory /artefacts/myfancysoftware-1.2.3/*.zip or
even /artefacts/myfancysoftware-1.2.3.zip (if you can place all your
artefacts in one zip file)

The advantages of this approach are:
1) you get a directory with downloadable versions of your product
2) it's easily automateable (either your build scripts create the tag and
place the artefacts with in the correct name in the correct directory, or you
create the tag and a post commit hook starts the build and commits the

Apart from that i favor the solution not to put build artefacts in a
repository (because most often they are big binary files, sometimes even CD
images). I rather ensure that everything needed to rebuild from a tag is
included in that tag.


On Tuesday 31 October 2006 14:01, Cornwell, Ian H wrote:
> We are in the process of migrating to subversion.
> We are having a discussion on how we should tag our built artefacts /
> deployment bundles.
> We are sure we want to include our deployed artefacts in the repository.
> We see 2 viable options, but we have not yet agreed which is best.
> Let's assume that we already have a source tag, and that we have built
> that and produced a set of files for deployment.
> Option A) Commit the deployment files to trunk (or a branch), and make
> another release tag from trunk (or a branch).
> Option B) Commit the deployment files straight to a new tag in tags/
> without them ever having been in trunk.
> Different engineers here see different advantages and disadvantages in
> the two options. It could be an advantage not to have the deployment
> files in trunk, because we are only ever interested in tags of
> deployment files.
> What do you think is the best practice for tagging deployment files?
> Ian
> -------------------------
> Mott MacDonald Ltd.
> 1 Atlantic Quay
> Broomielaw
> Glasgow G2 8JB
> Direct tel: +44 (0)141 222 4576
> -------------------------
> This message is from Mott MacDonald Limited, registered in England
> number 1243967. Registered office: St Anne House, 20-26 Wellesley Road,
> Croydon, Surrey, CR9 2UL, England.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 31 14:30:43 2006

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.