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

RE: automating versioning with tortoise svn

From: Phil Sayers <Phil_at_cds-am.net>
Date: Thu, 19 Aug 2010 09:27:08 -0400

It's not completely clear from your original post.. but...

We use a build server... cruisecontrol.net which manages versioning with the
following kind of process.
It is free.. there are other products out there for free and pay.

(all this is automated)
Fetch files from svn
Edit some xml files to increment version numbers based on last successful
build number stored by cruisecontrol.net
Compile the source into dll's & .exe's
Tag the branch in svn with a tag label of the version number that was
generated. So the edited xml files with the correct version number end up
in the tagged branch.
Deploy the dll's & exe's to an "installs" folder on our LAN and some
zipfiles in our website.

If you are only using svn as a place to store and make sure that everyone
has the same version of some files....you may want to look at the idea of a
"build & deploy"... when the build isn't really a compile... just a "version
it" and "deliver it" process.

You should also think about if every single commit means a new version
increment. What if you make a mistake in the commit?

We require versioned builds to need a human "1-click" to fire them off.
We've worked hard to get it down to 1-click, but it saves getting new
versions & release every single commit...which can be a huge time sink when
you make a mistake in the commit.

The bottom line is... script it.
Batch file, nant build file maybe or other scripting language.

-----Original Message-----
From: Vlad [mailto:vlad.sergeev_at_gmail.com]
Sent: Thursday, August 19, 2010 8:15 AM
To: users_at_tortoisesvn.tigris.org
Subject: automating versioning with tortoise svn

Hi all,

I have the following problem. The company that i work for uses
TortoiseSVN with in-house VBA tools. Tools are stored in repository
and read the version number from a text file that is stored along with
xls file. Every time we tag a release, we use this version number as
the tag name. Every time the version is increased and new tag
created, we need to change version number in two places - text file
and name of the tag. The idea is to do it once.

One idea was incrementing the version number in the file (based on the
tag name) inside of the pre-commit hook on the server side. But of
course, interfering with transaction object is not the most graceful
and legal way of doing (not sure if it is even possible).

Another idea is to customize the TortoiseSVN so that tagging a branch
would automatically pick up the tag name from the text file.

I would like to know what's possible and wouldn't mind hearing
alternative ideas

Thanks in advance,



To unsubscribe from this discussion, e-mail:


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-19 15:32:27 CEST

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

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