On Jul 7, 2008, at 05:38, HAcland wrote:
> I sort of worked out that I should be using 'svn update'. I have
> written the
> following post-commit.bat file:
>
> D:
> cd D:[my file path]\workingCopy\
> PATH C:\Program Files\subversion\svn-win32-1.4.6\bin\;
> mkdir demoDirToShowItIsBeingRunOK
> svn update
>
> This post-commit.bat file runs fine from the command line: it
> performs the
> svn update on the required working copy. However, when I perform a
> commit
> from a remote PC (using Tortoise) the post-commit hook runs fine
> (because I
> can now see a newly created directory
> 'demoDirToShowItIsBeingRunOK') but the
> crucial 'svn update' command is not being run. I am thinking this
> is to do
> with permissions but am a loss to explain it...
It could be that it's asking for credentials (username/password).
These were probably already cached when you ran it from the command
line, but when the hook script is being run it's happening as a
different user so it doesn't have that information cached. You may
need to supply it using the --username and --password arguments. You
should also use the --non-interactive argument since a hook script
cannot be interactive with the svn command. You should write the
error output of svn update to a file so that you can examine its
contents and see what's actually going wrong. Like (I think this
works on Windows too):
svn update 2 > C:\[someplacethisusercanwrite]\svn.error.log
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-07 20:26:56 CEST