On 10/13/06, Phyrefly <phyrefly.phyre@gmail.com> wrote:
>
>
> There are 4 zones within our environment, dev, test, staging and prod.
> The promotion from zone to zone is handled by a script (no human
> intervention) which will also label the repo when I get this working.
In svn, labeling is done as a copy to another path. Our repo is layed out
something like this:
code
trunk
tags
4.0
4.1
How are you planning to layout your repo?
Separate to this, I have a sandbox server, where I am playing with SVN
> at the moment.
>
> The repo will sit on the dev server, separate to the dev environment.
>
> Ideally, the developers will not have direct access to the dev
> environment at all, they will check out whatver files they need (to a
> local folder), modify them (local copy), commit (hook script updates
> dev version), and see the impact of their changes immediately on dev.
> So dev will be a reflection of the HEAD version, and real "working"
> working copies will be local for each developer.
>
> Does that help? I'm not sure what details you need, so may be giving
> too many, or the wrong ones :P
Yes, those are the details I needed. Unless you're talking about 10+
thousands of files and directories, there is no need to attempt to determine
what has changed in your hook script. "svn update" will update only modified
paths and files.
I used svnadmin to create my repo, so I know that works. and svnserve
> with those parameters works too. When I run svnserve like that, it is
> listening on port 3690, but when I run it through svnservice, it
> listens on a random port, as I described before.
In 1.4, use of svnservice is no longer necessary. Read
http://svn.collab.net/repos/svn/tags/1.4.0/notes/windows-service.txt for the
details.
> You should be able to use either the svn client or TortoiseSVN to connect
> to
> > svn://localhost and view the repo. You won't be able to make any changes
> > though until you either add yourself to C:\tmp\svn\conf\passwd or enable
> > anonymous changes in svnserve.conf.
>
> I can't connect to svn:// at all, I get an "actively refused" message
> (whether svnserve is listening on 3690 or another port). If I connect
> through file:// it works fine.
Searching Google shows a number of reasons why you might see this error. My
personal experience was with Windows XP & 2003's software firewalls although
anti-virus, routers, spyware, and adaware software are also mentioned. It's
definitely an OS error message though and not a problem caused or fixable
via svn configuration.
Received on Fri Oct 13 17:02:20 2006