Hi all!
I have a project on which I'm trying setup some build automation. I
think I've discovered a good way to revision these builds - I just use
the highest SVN revision number as the component or package revision
(eg, xyz-1.0-3454.tar.gz, where 3454 is the component high revision
number).
Two questions:
1. Has anyone ever done anything like this before? Some people use a
build number, and just keep incrementing it for every build they do. The
nice thing about the SVN revision number technique is that it's
automatically bumped whenever anything changes. You can even use it to
tell if you even NEED to build (same as last time? - no need for another
build). Any ideas in implementing such a schema are very welcome.
2. Is there a good way to GET the high SVN revision number for a
sub-directory of a project? Right now, I'm using a php script to call
'svn info --non-interative -R' on the repository url and sub-directory
(not a work area), and then just scanning for the highest value in the
repository for that subtree.
Thanks in advance,
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 1 19:57:36 2006