We have 3 environments for our web app; dev, beta and production. For
release management purposes, I need to create some tags but don't want
to have a large number of them, to keep confusion levels to a minimum.
Plus, because we want to use Anthill for build management (removing
the need for someone to log onto the server directly), I can just
point the projects in Anthill at a single tag and never have to change
it.
I'm reading Bill Nagel's book, and in chapter 12.1, he discusses
"sliding tags" and I think they may be the way to go. In doing so,
one creates a tag (/tags/beta for example), and just applies an
svn:externals property to it, pointing at the correct revision. So,
my question, as an inexperienced externals user, is "does the process
below make sense?"
0) We decide that /project/trunk at rev 172 is solid in dev, and ready for beta
1) Set svn:externals on /project/tags/beta to point at
http://server/Repos/project/trunk@172. Assuming no other commits have
happened, we're now at rev 173, correct?
3) Build in beta from http://server/Repos/project/tags/beta
2) We complete beta testing and we're satisfied with the results. No
other commits have happened in the repository.
3) Set svn:externals on /project/tags/production pointing at
http://server/Repos/project/tags/beta@173
4) Build in production from http://server/Repos/project/tags/production
Am I correctly understanding that if I have another release from dev
to beta, let's say revision 180, my production tag will still
represent the state of the code at revision 173 and I can make new
beta versions all day long and still keep getting the same result from
production, because I haven't changed where svn:externals points for
the production tag? Any "gotchas" I should be aware of?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 16 20:58:48 2006