That's odd since running svn update from the command-line on the server
doesn't prompt for anything. Might this be because it's in a commit script?
I also noticed that svn export works just as well; it seems to properly
export the new HEAD from the repository, and it will overwrite old files
it the "--force" directive is used. Is svn export a save way to do this,
since I will never commit from this working copy?
Ryan Schmidt wrote:
> On Aug 24, 2009, at 03:51, Jake Stone wrote:
>> I am running SVN over Apache on Windows Server 2003, and I am trying to
>> create a post-commit script for an ArgoUML repository. The repository
>> only holds their ".zargo" files, and there is a nice command-line method
>> to generate SVG diagrams from their UML projects, and I want to create a
>> hook to do so automatically.
>> I've created a checkout on the SVN server, but when I add "svn update
>> %REPOS%" to my post-commit hook, any commits to that repository
>> complete, but the post-commit hangs indefinitely. When I cancel the
>> commit, the server's checkout requires svn cleanup and svn update to
>> properly bring it up to date.
> The svn update command is probably waiting to receive a username and
> password. Use the --non-interactive option to prevent this waiting.
> Once you do, it shouldn't hang, but will probably exit with an error
> telling you it doesn't know what username and password to use. You may
> then need to use the --username and --password options to feed it the
> correct username and password. You should be catching and recording
> any error messages coming from the svn update command, and any other
> command in your hook script, perhaps in a logfile.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-24 11:09:55 CEST