SVN Post Commit Hook Batch Windows

3
votes

I have a Windows Server running Visual SVN Server to store our repositories. Also on that server is our test copy.

I'm trying to set up a simple SVN post-commit hook so it updates that test copy automatically every time I commit something

In Visual SVN in the post-commit hooks I've set up like this

"C:\Program Files (x86)\VisualSVN Server\bin\updatescripts.bat" D:\inetpub\TESTCOPY

Then that batch file has a simple update like this

PATH=%PATH%;"C:\Program Files (x86)\VisualSVN Server\bin\"
svn update %1

If I run the batch file in the server by double clicking on it or from command line works fine. When committing something from my laptop it freezes and doesn't give me any error and locks the test copy so then I need to go in and run a clean up.

Visual SVN service is running as network service and this aacount has full access to the bin folder and the test copy on the server.

Any idea how to set up a simple svn update post commit hook anyone?

Thanks Fede

4
windowsbatch-filesvnvisualsvn-serverpost-commit-hook
I am attempting the same thing, I unsuccessfully tried to do everything within the hook itself then found this approach. I get strange results, ultimately it does not update however when I just double click the batch file it works. When I change the name of the batch file in the post-commit hook it gives me an error saying it can't find the file. So it seems the hook can find the file but doesn't execute it? I dunno but here is what I have. In post-commit hook: "C:/my path/myrepository/file.bat" In batch file: cd "C:/working path/myrepository" svn update Anyone see any issues? – mgrenier
When you install VisuaSVN Server it adds %VISUALSVN_SERVER% environment variable. Check it. – bahrep

4 Answers

1
votes

I had a similar problem and it turned out to be that SVN likes paths to use forward slashes instead of backslashes.

Try this:

set MYPATH=%1

:: Transform backslashes to forward slashes
set MYPATH=%MYPATH:^\=/%

svn update %MYPATH%
1
votes

You're running the svn update command. Exactly what working copy are you trying to update?

The parameter being passed is the Repository's path. This points not to a working directory, but to the directory that contains the Subversion master repository. This is the same directory where your post commit hook is stored.

Subversion hooks do not have access to the user's working directory, so you can't manipulate the user's files. Hook scripts usually should be using svnlook and not svn. By doing this, you prevent yourself from getting into any sort of trouble.

It is possible to update a Subversion working copy on the server, if you know the location:

PATH=%PATH%;"C:\Program Files (x86)\VisualSVN Server\bin\"
set SVN_WORK_DIR=C:\SVN\workdir"
svn update %SVN_WORK_DIR%

However, I wouldn't recommend this because it ties up Subversion. The user who did the commit would have to wait until the update is complete before Subversion returns the control of the prompt back to the user.

0
votes

After trying a million different things this worked for me...

I put this in my post-commit hook "C:\Program Files\VisualSVN Server\bin\svn.exe" update "C:\my path\" where my path is the path to the working copy to be updated

Also I had to change the service to run as local system

0
votes

That is really not the way you want to do that. What you should do is use something like Jenkins to watch your repository. Jenkins can watch your repository, and it when it changes, update your test copy, kick-off builds, run automated tests, etc.