On 10/22/07, Bicking, David (HHoldings, IT)
<David.Bicking@thehartford.com> wrote:
>
> > -----Original Message-----
> > From: Andy Levy [mailto:andy.levy@gmail.com]
> >
> > On 10/22/07, nav@ciklum.net <nav@ciklum.net> wrote:
> > > Thanks!
> > > But here is one more question:
> > >
> > > there are actually several sites we're going to work on, and these
> > > sites use some common components.
> > > Website1 = Solution1 = Project1 + Project2
> > > Website2 = Solution 2 = Project3 + Project2
> > >
>
> <snip>
>
> >
> > Symlinks don't work on Windows, so that might pose a problem.
> > Use svn:externals to pull Project2 into the other projects.
> >
> > svnlook changed in your post-commit will show you what's been changed.
> > Parse the paths and take the appropriate action based on
> > what's changed.
> >
> <snip>
>
> >
> > SVN looks for .bat, .cmd and .exe files when executing hooks.
> >
> > Do you really want to do an export each time? Depending upon
> > the size of the project, that could take a while. Make each
> > site under wwwroot a working copy, then you can update with a
> > much-faster svn update.
> >
>
> For development, I'd do what you suggest, Andy. When it comes time for
> "production deployment", I'd have some kind of managable process.
Oh, absolutely. I wish I could even have an auto-deploy for my
development environments, but our promotion process has to be really
strictly controlled at every step of the way thanks to SOX controls.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 22 15:51:00 2007