Feb 10, 2011 at 7:01 AM
Edited Feb 10, 2011 at 7:02 AM
Where can I get the pre-commit hook scripts required to get the revision history from VSS to SVN?
Aug 6, 2011 at 10:40 AM
Edited Aug 6, 2011 at 10:42 AM
Hey, I finally got it working, create a file pre-revprop-change.bat under your svn hook folder like C:\svn_repository\myproject\hooks
:: Set all parameters. Even though most are not used, in case you want to add
:: changes that allow, for example, editing of the author or addition of log messages.
:: Only allow the log message to be changed, but not author, etc.
:: if /I not "%propertyName%" == "svn:log" goto ERROR_PROPNAME
:: Only allow modification of a log message, not addition or deletion.
:: if /I not "%action%" == "M" goto ERROR_ACTION
:: Make sure that the new svn:log message is not empty.
for /f "tokens=*" %%g in ('find /V ""') do (
if "%bIsEmpty%" == "true" goto ERROR_EMPTY
echo Empty svn:log messages are not allowed. >&2
echo Only changes to svn:log messages are allowed. >&2
echo Only modifications to svn:log revision properties are allowed. >&2
exit /b 1
also you may need to create another file post-commit.bat in the same hook folder as well,
# POST-COMMIT HOOK
# The post-commit hook is invoked after a commit. Subversion runs
# this hook by invoking a program (script, executable, binary, etc.)
# named 'post-commit' (for which this file is a template) with the
# following ordered arguments:
#  REPOS-PATH (the path to this repository)
#  REV (the number of the revision just committed)
# The default working directory for the invocation is undefined, so
# the program should set one explicitly if it cares.
# Because the commit has already completed and cannot be undone,
# the exit code of the hook program is ignored. The hook program
# can use the 'svnlook' utility to help it examine the
# newly-committed tree.
# On a Unix system, the normal procedure is to have 'post-commit'
# invoke other programs to do the real work, though it may do the
# work itself too.
# Note that 'post-commit' must be executable by the user(s) who will
# invoke it (typically the user httpd runs as), and that user must
# have filesystem-level permission to access the repository.
# On a Windows system, you should name the hook program
# 'post-commit.bat' or 'post-commit.exe',
# but the basic idea is the same.
# The hook program typically does not inherit the environment of
# its parent process. For example, a common problem is for the
# PATH environment variable to not be set to its usual value, so
# that subprograms fail to launch unless invoked via absolute path.
# If you're having unexpected problems with a hook program, the
# culprit may be unusual (or missing) environment variables.
# Here is an example hook script, for a Unix /bin/sh interpreter.
# For more examples and pre-written hooks, see those in
# the Subversion repository at
# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
commit-email.pl "$REPOS" "$REV" firstname.lastname@example.org
log-commit.py --repository "$REPOS" --revision "$REV"
exit /b 0
Jun 28, 2013 at 3:43 PM
all you need is a pre-revprop-change hook that returns 0 (ie. it responds with 'changes are ok'). That's it. The SVN docs describe this.