Hi Olga,

Thank you for the response. We are using VisualSVN Server 1.6.2 on a
Windows 2008 server. In my post-commit hook, I tried using code like:

"c:\program files\visualsvn server\bin\svn.exe" export file:///%1/trunk
d:\inetpub\bsweb\_developers\sbs\testexport --quiet --non-interactive
--force

This results in an error message :
Warning: post-commit hook failed (exit code 1) with output:
Warning: svn: Unable to open an ra_local session to URL
Warning: svn: Unable to open repository 'file:///D:%5CRepositories
%5Ctest_program%5Ctrunk'
Warning: svn: Can't open file '\D:\Repositories\test_program\trunk
\format': The filename, directory name, or volume label syntax is
incorrect.

However, this works just fine:
"c:\program files\visualsvn server\bin\svn.exe" export
http://192.168.0.188:8080/svn/test_program/trunk d:\inetpub\bsweb
\_developers\sbs\testexport --quiet --non-interactive --force --
username myusername --password mypassword

As we have about 80 projects to put under Subversion, I'd prefer to
use the variable rather than hand coding for each project. Any ideas?


On Jan 26, 10:48 am, VisualSVN Support <[email protected]> wrote:
> Hi!
>
> Please could you provide details about your configuration:
>  - what version of VisualSVN Server do you use?
>  - what version of Windows do you use?
>
> Could you also send us an example of your path and your command line?
>
> Thank you!
>
> On Thu, Jan 22, 2009 at 11:51 PM,  <[email protected]> wrote:
>
> > I've tried and tried to create a post-commit hook to export the
> > repository to a directory. It works if I hard code the path in, or if
> > I use http:// and hard code the url in. I'd like to use the variable
> > that VisualSVN Server says is available as %1 (path to the
> > repository), but it appears that variable is url encoded, so slashes
> > are showing up as %5C, and the command line isn't able to connect to
> > the repository. Is there a way to change this behavior, or am I forced
> > to hard code the paths in for every repository we have?
>
> --
> Olga Dolidze
> VisualSVN Support

Reply via email to