On Mon, Feb 25, 2008 at 8:05 AM, Jay Smith <jaysmailinglist_at_gmail.com> wrote:
> Mark, thanks for the tidbits, they defintely clear up a lot.
>
> Armed with my novice yet growing knowledge, I was thinking about treating
> the product web directory as working space and having an svn update script
> of some sort croned. The switch options sounds interesting though.
Keep in mind that switch and update are essentially the same thing.
The former simply allows you to change the URL the working copy is
connected with and then does an update.
> If I used the tags directory as the master for updates, where do developers
> committ to and update from? I'm guessing trunks (since tags is copy). My
> update process for production could watch either the trunk or the tags
> directory, but tags is better (faster more efficient)... is this correct?
This is not about speed, it is about implementing the SCM process that
matches what you want to accomplish.
Do you pretty much want to push changes out to the web site as soon as
they are made? If so, then checkout trunk to the web site location
and have developers commit to trunk. You can either have a hook
script update the working copy, or just setup a scheduled job to run
every hour automatically. When you occasionally get a change that
needs longer development and testing simply create a branch, do the
work in that branch and test. When it is ready, merge the branch to
trunk.
Would you rather do release-based deployment? In other words, do a
bunch of changes and test them before deploying? In that case, make a
tag for the release and have the tag checked out on the web site. Do
your development in trunk (with branches as needed) and when you have
everything ready for a new release make a new tag. Then use the svn
switch command to point the web site to the new tag.
Want a hybrid of these two approaches? Do your development on trunk
(with branches as needed). Create a "production" branch from trunk
that the web site has checked out. Use merge to merge changes from
trunk to the production branch when you want to deploy them. Have a
hook script or scheduled job that regularly runs update.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-25 15:22:32 CET