View source for SVN Tips

From Opentaps Wiki

← SVN Tips

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: Users.
• This page has been protected to prevent editing or other actions.

---

You can view and copy the source of this page.

== Setting up Commit Emails == Before we begin, ensure that mail can be sent from the server on which the subversion repository lives. If you're on a UNIX OS, this can be done by running the mail program from the command line, prompt:> mail -s "test subject" someone@somewhere.com Type in body of email and press CTRL-D to send. ^D prompt:> Next, go to the <tt>hooks/</tt> directory of our subversion repository. It should contain several files ending in <tt>.tmpl</tt>. These are shell script templates that allow you to hook actions to subversion events. In particular, we are looking for <tt>post-commit.tmpl</tt> which we will use to send email whenever a commit is made. * Ensure that <tt>commit-email.pl</tt> exists in <tt>hooks/</tt> directory. If you cannot find it, [http://subversion.tigris.org/tools_contrib.html#commit_email_pl get it from here]. * Create a copy of <tt>post-commit.tmpl</tt> named <tt>post-commit</tt> * Edit <tt>post-commit</tt> and add the following before the call to <tt>commit-email.pl</tt> PATH=/path/to/subversion/hooks * Comment out log-commit.py if present, it's not necessary. This script only needs to do commit-email.pl * Specify the email or space separated list of emails to send these commit notifications to as the last arguments to commit-email.pl * Make sure that commit-email.pl and post-commit are executable by anyone chmod a+x commit-email.pl post-commit This should basically be it. Commit something to test things out. If there is a problem, it will usually show up in the mail server logs. The next sections cover possible issues. == Permission Denied == If you're running svnserve to allow checkout using svn:// URL notation, then you have to make sure that the user that runs svnserve can also read and execute the scripts in hooks/. Make sure this user owns that directory and all files in it. You might also want to make sure this user can send emails to the mailserver. Log in as the user and use the mail command to test this.

Return to SVN Tips.