#!/bin/sh# PRE-COMMIT HOOK
#
# The pre-commit hook is invoked before a Subversion txn is
# committed. Subversion runs this hook by invoking a program
# (script, executable, binary, etc.) named 'pre-commit' (for which
# this file is a template), with the following ordered arguments:
#
# [1] REPOS-PATH (the path to this repository)
# [2] TXN-NAME (the name of the txn about to be committed)
#
# [STDIN] LOCK-TOKENS ** the lock tokens are passed via STDIN.
#
# If STDIN contains the line "LOCK-TOKENS:\n" (the "\n" denotes a
# single newline), the lines following it are the lock tokens for
# this commit. The end of the list is marked by a line containing
# only a newline character.
#
# Each lock token line consists of a URI-escaped path, followed
# by the separator character '|', followed by the lock token string,
# followed by a newline.
#
# The default working directory for the invocation is undefined, so
# the program should set one explicitly if it cares.
#
# If the hook program exits with success, the txn is committed; but
# if it exits with failure (non-zero), the txn is aborted, no commit
# takes place, and STDERR is returned to the client. The hook
# program can use the 'svnlook' utility to help it examine the txn.
#
# On a Unix system, the normal procedure is to have 'pre-commit'
# invoke other programs to do the real work, though it may do the
# work itself too.
#
# *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT ***
# *** FOR REVISION PROPERTIES (like svn:log or svn:author). ***
#
# This is why we recommend using the read-only 'svnlook' utility.
# In the future, Subversion may enforce the rule that pre-commit
# hooks should not modify the versioned data in txns, or else come
# up with a mechanism to make it safe to do so (by informing the
# committing client of the changes). However, right now neither
# mechanism is implemented, so hook writers just have to be careful.
#
# Note that 'pre-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
# 'pre-commit.bat' or 'pre-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.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/ and
# http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/REPOS="$1"
TXN="$2"# Make sure that the log message contains some text.
SVNLOOK=/usr/bin/svnlook
# $SVNLOOK log -t "$TXN" "$REPOS" | \
# grep "[a-zA-Z0-9]" > /dev/null || exit 1# 通过svnlook获取提交时的日志信息
LOGMSG=$( $SVNLOOK log -t "$TXN" "$REPOS" | grep "[a-zA-Z0-9]" | wc -c )# 判断日志长度
if [ "$LOGMSG" -lt 1 ]; then
echo -e "\n 警告：必须填写注释！" 1>&2
exit 1
fi# Check that the author of this commit has the rights to perform
# the commit on the files and directories being modified.
# commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1# All checks passed, so allow the commit.
exit 0

使用 hook ，为了方便管理员 控制提交的过程 Subversion 提供了 hook 机制。当特定的 事件发生时，相应的 hook 会被调用， hook 其实就相当于特定 事件的处理函数。每个 hook 会得到与它所处理的事件相关的参数，根据 hook 的 返回值， Subversion 会决定是否继续当前的提交过程。

当前 Subversion 提 供了 5 种可以安装的 hook ：

hook 只有安装之后才 会被执行，在 Subversion 中这一过程相当简单。只需将 hook 放 在代码库目录的 hooks 子目录下即可。为了能顺利地找到它们， Subversion 规 定 hook 的 命名与上表的事件名同名，如 pre-commit 的 hook 名就是 pre-commit （请 确保它是可执行的，在 windows 平台下需要添加对应的扩展名，如 bat 、 exe 、 com 。）。 创建代码库之后， Subversion 会创建对应的这 5 个事件的 hook 模 版。选取所需的模版，然后将其改名，在修改内容。这样 hook 就可以工作了，当 然请先确保 hook 本身能正常的执行。

hook 的编写非常简 单，通常的做法：

-         法 1 ： 使用所在平台的脚本语言，如 unix 下的 shell ，或 windows/dos 的 批处理命令。

-         法 2 ： 使用相关的语言，如 c 。

-         法 3 ： 使用脚本语言，如 Python 或 perl 等实现主体。然后 通过法 1 来调用。

-         法 4 ： 使用相关的语言实现主体，然后通过法 1 来调用。

这里给出在 windows 下 使用 bat 的例子，它实现了 pre-commit hook 主 要作用是检查提交内容中是否包含说明信息，如果没有就放弃：

由于平台的脚本系统功能毕竟 有限（ unix 下的不太清楚，不过批命令就太差了），建议采用方法 2 、 3 和 4 。 从简易性方面的考虑，推荐方法 3 。因为象 python 就已经提供了 一些常用的功能，如发送邮件。

最后，就是 subversion 以 正在存取代码库的过程的所属用户来执行 hook 。因此，请确保这个用户具有足够的权限，可以访问 hook 可 以直接或间接访问的资源。