Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Sending commit messages via mail must be configured by a Codehaus administrator. Administrators should initially configure this on behalf of project committers. The following procedure should be done on beaver.codehaus.org.

  1. cd into the repository's hooks directory. For example:
    No Format
    cd /home/projects/FOO/scm/hooks
    
  2. Create a post-commit file and make it executable (sudo chmod 755 post-commit). The contents of the file should include the following (Note: you must change "FOO" to the name of the new repository):
    • To use SVN::Notify
      No Format
      #!/bin/sh
      
      REPOS="$1"
      REV="$2"
      PATH=/usr/bin:/bin:/usr/local/subversion/bin
      PROJECT=FOO
      JIRA_URL=http://jira.codehaus.org/secure/ViewIssue.jspa?key=%s
      FISHEYE_URL=http://fisheye.codehaus.org/changelog/FOO/?cs=%s
                
      # Note that --from is optional and if omitted the from address will be $COMMITTER@codehaus.org
      # JIRA and Fisheye are also optional
      svnnotify --repos-path "$REPOS" \
                --revision "$REV" \
                --svnlook /usr/local/subversion/bin/svnlook \
                --to scm@$PROJECT.codehaus.org \
                --from scm@$PROJECT.codehaus.org \
                --with-diff --subject-cx --handler HTML::ColorDiff \
                --jira-url $JIRA_URL \
                --viewcvs-url $FISHEYE_URL
      
    • To use Subversion's standard boring script:
      No Format
      #!/bin/sh
      
      REPOS="$1"
      REV="$2"
      PATH=/usr/local/subversion/share/tools/hook-scripts
      
      commit-email.pl -s "[FOO]" "$REPOS" "$REV"  scm@FOO.codehaus.org
      
  3. Clean up permissions and group ownership in hooks directory (make sure you are in the "hooks" directory!!):
    No Format
    sudo chgrp groupname post-commit
    sudo chmod g+w post-commit
    

Changing the reply-to address for an scm list

This is not recommended, since it leads to dissemination via the list of messages returned from bad auto-responders and MTAs. Also, it may lead to public replies to the list where personal replies were intended. In addition, the original ``Reply-To:'' header is lost.

If you do want to add a reply-to list header, put

Code Block
reply-to

into /home/projects/FOO/scm/headerremove, and

Code Block
Reply-To: list@host.dom

into /home/projects/FOO/scm/headeradd.