Как настроить скрипт post-commit в SVN для обновления измененных файлов?

Я удалил post-commit.tmpl, а в файле post-commit вот код:

#!/bin/sh

export LANG=en_US.UTF-8   
SVN_Path=/root/svn/myblog
WEB_Path=/home/app/myblog
echo `date "+%Y-%m-%d %H:%M:%S"`
$SVN_Path update --username xxx --password yyy $WEB_Path --no-auth-cache 

# 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="

I deleted post-commit.tmpl, and in post-commit file, here is the code:

#!/bin/sh

export LANG=en_US.UTF-8   
SVN_Path=/root/svn/myblog
WEB_Path=/home/app/myblog
echo `date "+%Y-%m-%d %H:%M:%S"`
$SVN_Path update --username xxx --password yyy $WEB_Path --no-auth-cache 

# 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"

# mailer.py commit "$REPOS" "$REV" /path/to/mailer.conf

Unfortunately, nothing will happen in my project file (project path is /home/app/myblog) after I commit my modified code to server. But if I execute this file in command line, I will get this info:

 2016-11-09 16:32:10
./post-commit: line 9: /root/svn/myblog: Is a directory

Meanwhile, in the follow path: /root/svn/myblog/db/revprops/0, I can find all commit log files. I guess it means the modified files are committed to server, right?

I am using CentOS, Express.

So, could anyone help me about this? Thx!!

"
# REV=""

# mailer.py commit "$REPOS" "$REV" /path/to/mailer.conf

К сожалению, ничего не произойдет в моем файле проекта (Путь к проекту /home/app/myblog) после того, как я зафиксирую свой измененный код на сервере. Но если я выполню этот файл в командной строке, я получу эту информацию:

 2016-11-09 16:32:10
./post-commit: line 9: /root/svn/myblog: Is a directory

Тем временем, в следующем пути: /root/svn/myblog/db/revprops/0, я могу найти все файлы журнала фиксации. Я думаю, что это означает, что измененные файлы зафиксированы на сервере, верно?

Я использую CentOS, Express.

Кто-нибудь может мне помочь? Thx!!

1 ответ

  1. 2016-11-09 16:32:10 ./post-commit: line 9: /root/svn/myblog: Is a
    directory

    Согласно коду, $SVN_Pathдолжен указывать на клиента командной строки Subversion svn. Но вместо этого он указывает на каталог/myblog:

    SVN_Path=/root/svn/myblog

    Необходимо настроить $SVN_Pathуказатель на svnклиент на компьютере.

    Между тем, в следующем пути: / root / svn/myblog/db / revprops/0, я могу
    найти все файлы журнала фиксации. Я думаю, что это означает, что измененные файлы
    зафиксировано на сервере, верно?

    Крючки после фиксации выполняются после фиксации. Итак, да, фиксация попала в репозиторий. Однако крюк не сработал из-за опечатки$SVN_Path.