I’m trying to troubleshoot a post-commit hook script issue. I need to be able to try different solutions and see if they fix the problem by having Subversion run through its post-commit trigger — this is critical because the problem lies with the particular user account running the post-commit script and its environment. (our setup is SVN/Apache, where Apache is running as LocalSystem on Server 2003)
Anyway, filling up the repository with bogus “test only” changesets is sub-optimal. Is there a better way to tell Subversion to pretend that a real changeset has been committed and to run through the post-commit script?
A couple of things I might try:
Move your script to start-commit and intentionally return a non-zero value so the commit doesn’t happen. Depending on what you’re trying to work out, this should replicate the environment close enough to debug.
Execute the script directly within a shell on the server.