0

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

首先，这些文件的权利

-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

post-commit 在禁用预提交脚本后运行（重命名为 .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

4

4 回答 4

0

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

于 2013-07-23T14:02:32.393 回答
0

有几个问题：

退出代码

预提交挂钩用于在提交之前执行检查。从文档中：

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

你完成了你的预提交

exit 2

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

权限

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

chmod +x pre-commit post-commit

-rw-r--r--意味着它们可以被所有者读取（和写入）但不能被执行。

社邦

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

#!/bin/sh

更新 1

您的更新的答案也在文档中：

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

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

echo "my message" 1>&2

更新 2

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

正如文档中所指定的那样，不会exit 2导致提交中止。它将通过（如果您想阻止提交，则必须在挂钩中进行）。由于您没有在标准错误中返回任何内容，因此客户端不会显示任何内容。（见我对你第一次更新的回答内容）pre-commit

添加类似的东西

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

到你的post-commit脚本

于 2013-07-23T14:02:40.413 回答
0

post-commit如果预提交返回错误条件，则永远不会触发。

于 2013-07-23T14:03:14.877 回答
0

这都是由于权限问题。

于 2013-07-31T18:19:43.503 回答