RE: Re: I, too, miss tags.

> > If a tag was created off another tag,
>
> Huh? Tag of tags? What a heck is it and how can I avoid it?
>
> > it will also let you dig further
> > down.

I use tags to help manage automated build processes. Each environment
that is built/deployed by CruiseControl has a corresponding tag:

/env/qa
/env/uat
/env/prod

Whenever a build completes successfully, CruiseControl tags the
repository to preserve the version of the codebase the build was created
from:

/builds/qa/build.1

A QA build is promoted to UAT after our QA people sign off, a UAT build
is promoted to PROD after the client signs off. So by the time a build
hits Production, the log of the prod build tag could look something like
this:

/builds/prod/build.1
        Copied from: /env/prod:200
                Copied from: /builds/uat/build.1
                        Copied from: /env/uat:190
                                Copied from: /builds/qa/build.1
                                        Copied from: /env/qa:180
                                                Copied from:
/branches/project1:170

This way, I have an audit trail that tells me exactly who promoted what
to where and when. Any developer can go into SVN and grab /env/prod to
find out what's currently in Production and how it got there.

Cheers
Rob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 27 20:05:06 2006