Subversion (software)

Blog Archive » Subversion post commit email hook, in Ruby I’m a big believer in tools. Personally, I believe that better engineers tend to use better tools, but that’s a subject to explore in another post. Here’s a handy Ruby script that sends a descriptive email after each subversion checkin. The script is based on the one written by Elliott Hughes. Somehow I seem to rewrite this script every time I take a new job, so I’m pleased to release this one into the public domain. The script lists all files that were added, removed, or modified. If you’re going to use this with a sizable engineering team, I recommend changing the HTML email to include a photo of the person who committed the change. Also, it’s nice to have the “modified” lines link to the diff. Please excuse my amateurish Ruby. To install: Copy the script to hooks/post-commit in your subversion repository.Make the script executable.Modify the ADDRESS constant at the top of the file. You can download the script or copy and paste it from below:

Version Control with Subversion XP-Dev.com - Subversion Hosting, Project Tracking & Agile To A better Subversion post-commit hook than <tt>commit-email I finally got round to automating sending out commit emails for our Subversion repositories. I tried the supplied post-commit.tmpl and commit-email.pl, but they suck. Six hundred lines of Perl and no effort made to color the patch or format the check-in comment? I knocked up something that isn't going to win any beauty contents unless it's only up against commit-email.pl, in which case it should be a walk-over. Here's the script; as usual, the latest version will be in salma-hayek: #! # A Subversion post-commit hook. # You *will* need to change these. address="software@jessies.org"sendmail="/usr/sbin/sendmail"svnlook="/opt/subversion-1.1.0-rc2/bin/svnlook" require 'cgi' # Subversion's commit-email.pl suggests that svnlook might create files.Dir.chdir("/tmp") # What revision in what repository? # Get the overview information.info=`#{svnlook} info #{repo} -r #{rev}`info_lines=info.split("\n")author=info_lines.shiftdate=info_lines.shiftinfo_lines.shiftcomment=info_lines body = ""

Version Control with Subversion Before jumping into the broader topic of repository administration, let's further define what a repository is. How does it look? How does it feel? Does it take its tea hot or iced, sweetened, and with lemon? As an administrator, you'll be expected to understand the composition of a repository both from a logical perspective—dealing with how data is represented inside the repository—and from a physical nuts-and-bolts perspective—how a repository looks and acts with respect to non-Subversion tools. The following section covers some of these basic concepts at a very high level. Understanding Transactions and Revisions Conceptually speaking, a Subversion repository is a sequence of directory trees. Every revision begins life as a transaction tree. Updates work in a similar way. The use of transaction trees is the only way to make permanent changes to a repository's versioned filesystem. Transactions and revisions in the Subversion repository can have properties attached to them. Warning conf