Question

我的基本提交后脚本不会触发。但是，我的预提交脚本没问题。

首先，这些文件的权利

-rw-r--r-- 1 apache apache 3426 Jul 23 09:02 pre-commit
-rw-r--r-- 1 apache apache 2106 Jul 23 08:38 post-commit

Pre-commit文件内容：

REPOS="$1"
TXN="$2"
exit 2

错误捕获

Some of selected resources were not committed.
svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 255) with no output.
svn: MERGE of '/post-commit-tests/trunk': 409 Conflict (http://mydomain.com)

Post-commit文件内容

REPOS="$1"
REV="$2"
exit 2

不会抛出任何错误。

我正在通过Eclipse中的http检查/提交代码。

更新＃1

在禁用预提交脚本（重命名为.tmpl）之后运行提交后。

客户端是否应确认提交后的退出代码？

更新＃2

新权限：

-rwxr-xr-x 1 apache apache 2114 Jul 23 10:19 post-commit

这是提交后的整个文件

# !/bin/bash

# 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:
#
#   [1] REPOS-PATH   (the path to this repository)
#   [2] 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.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/ and
# http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/


REPOS="$1"
REV="$2"
echo "my message" 1>&2
exit 2

当我提交时，它仍然会在Eclipse中没有返回错误的情况下继续运行。但是，运行./post-commit将按预期输出。

更新＃3

SVN：1.6 Apache：2.2 使用DAV

Answer 1

您需要使脚本可执行：chmod +x pre-commit post-commit。

Answer 2

有几个问题：

退出代码

预提交挂钩用于在提交之前执行检查。来自documentation：

如果pre-commit挂钩程序返回非零退出值，则中止提交，删除提交事务，并将打印到 stderr 的任何内容编组回客户端。

你完成了预先提交

exit 2

将始终告诉Subversion中止提交。由于不会提交，因此永远不会执行提交后挂钩。

<强>权限

此外，两个脚本都应该是可执行的：

chmod +x pre-commit post-commit

-rw-r--r--表示可以阅读（并由所有者书写）但不执行。

<强>认领

您的脚本在开头缺少Shebang，指定应调用哪个解释器。如，

#!/bin/sh

更新1

您的更新答案也在documentation：

中

如果提交后挂钩返回非零退出状态，则提交将不会中止，因为它已经完成。但是，钩子打印到stderr的任何东西都会被编组回客户端，从而更容易诊断钩子故障。

代码不会发送到客户端，但是您输入标准错误的所有内容都会。例如：

echo "my message" 1>&2

更新2

在Shebang开头你仍然缺少#，但我认为这是一个复制和粘贴问题。

如具有exit 2的文档中所指定，不会导致提交中止。它将通过（如果你想阻止一个提交，你将必须在pre-commit钩子中）。当你不在标准错误上返回任何内容时，客户端将不会显示任何内容。（请参阅我对您第一次更新的回答的内容）

添加类似

的内容

echo "Error! Something went wrong after your commit!" 1>&2

到您的post-commit脚本

Answer 3

如果预提交返回错误条件，

post-commit将永远不会触发。

Answer 4

这完全归功于许可问题。

提交后没有解雇

4 个答案: