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

Re: Autodeploy with Subversion (merging giving me a headache)

From: Andrew Thompson <subversionuser_at_aktzero.com>
Date: 2005-03-03 20:04:57 CET

Johnson, Rick wrote:
> I'm having a very difficult time with merge tracking and have shot
> myself in the foot a couple of times. In my situation, I would much
> rather use Tags in the Production directory since that's really what I'm
> deploying. My problem is that I haven't figured out a way to have the
> autodeployment work with a directory full of Tags rather than just the
> files.
> Any suggestions would be helpful. I've thought of always having a
> "Current" Tag and renaming it and creating a new "Current" tag when it's
> time for a live build but that seems inelegant and doesn't impart any
> date/time or version information. It would probably be more elegant that
> what I've done to fix a screwed up merge though.

I asked a question a day or so ago that was regarding a "current" tag.
(Yes, I know, if it changes, it's not really a tag. And tag versus
trunk, it's all in our heads.)

I just did a svn help list and see that the -v (or --verbose) tag causes
more information to be dumped. The tags/ folder for my website looks like:

       3 athompso Feb 27 00:49 2005.02.26/
       5 athompso Feb 28 11:06 2005.02.27/

(Note that the tags were named for the period they represent, 2005.02.26
and 2005.02.27.)

It shouldn't be too difficult to dump that to a file and figure out
which date is the most recent and then read in the folder name.

Caveat: I don't know how this output would look if it contained a
committed folder from last year. That would have to be taken into

Andrew Thompson
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 3 20:08:29 2005

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.