2011/6/15 Henry Hartley <henryhart...@westat.com>: > Andy Levy wrote: >>> >>> Pass valid credentials to svn update with --username and --password >>> in your hook & see what happens. > > I'm finally getting back to this issue. Things have changed a little so > here's a recap and the current situation: > > I have a VisualSVN repository on a development web server with a web site > properly loaded. I checked out a copy with my client (Dreamweaver CS5). I > also have checked out a copy that is served as the development web site on > the same machine as the repository. So far, so good. > > I have a post commit hook (post-commit.bat) with the following line in it > (all one line and with minor changes to protect confidentiality): > > "C:\Program Files (x86)\VisualSVN Server\bin\svn" --username SVN_User > --password therealpw update D:/websites/site1
1. I'd add "--no-auth-cache --non-interactive" options as well, and "@echo off" at the start and "exit 0" line at the end. 2. http://subversion.apache.org/faq.html#website-auto-update 3. What protocol is used by the working copy at D:/websites/site1 (file, svn, http, https)? For https you may want "--trust-server-cert" as well. 4. What user runs the bat file? If it is "Local System" (if I correctly remember the name), it does not have rights to access the network. > Is there any way to increase the logging level of VisualSVN When debugging my hooks I used to add echo statements that wrote something to an external log file. Best regards, Konstantin Kolinko