[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: post-commit question/issue

From: Jeff Lanzarotta <delux256-subversion_at_yahoo.com>
Date: 2007-05-02 18:09:24 CEST

You will need to change the post-commit script to something like this:

----------8<----------

  #!/bin/sh
  # 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.collab.net/repos/svn/trunk/tools/hook-scripts/ and
  # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/

  export PYTHONSTARTUP=/etc/pythonstart
  export PYTHONPATH=$PYTHONPATH:/usr/local/lib/svn-python

  REPOS="$1"

  #commit-email.pl "$REPOS" "$REV" test@emailaddress.com
  #log-commit.py --repository "$REPOS" --revision "$REV"

  /usr/bin/python $REPOS/hooks/mailer.py commit "$REPOS" "$REV"
$REPOS/hooks/mailer.conf

----------8<----------

You will notice that I had to add PYTHONSTARTUP, PYTHONPATH, as well as
use absolute paths. These will need to be changed according to your OS
and installation setup.

--- Binod <binod3@gmail.com> wrote:

> Here when I say I changed post-commit.sh to post-commit, I have only
> one
> file called post-commit in the /home/svn/repos/hooks
>
> I just wanted to clarify that if that helps.
>
> Thanks and I hope some one can help me with this
>
>
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 2 18:10:16 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.