Straight Forward IT

To help ensure your team is providing useful detail regarding svn check-ins a pre-commit can be used to valid the commit message. Additional checks can be done to valid the task number against your Redmine Database/Jira Database. Locate your repository /path/to/repository/ cd hooks cp pre-commit.tmpl pre-commit edit the pre-commit file and the add code similar to below On the file is saved. Make is executable chmod 775 pre-commit A working script, CentOS(Linux) ver 6 using a Redmine database The pre-commit code checks the SVN commit for: 1. There is a commit message 2. The message starts with "Issue #nnnn" 3. The issue number nnnn is in the Redmine issues table in MySQL References: http://www.redmine.org/boards/2/topics/449 http://lisa-n-tom.com/blog/?p=29 http://www.zytrax.com/tech/web/regex.htm#simple http://stackoverflow.com/questions/8113289/svn-pre-commit-hook-failure http://blog.grimsy.net/2008/07/a-few-svn-pre-commit-hooks/ http://svn.haxx.se/...

Using Apache modules to expose SVN for your team(s). The following setup was performed on CentOS(ver 6) to expose SVN via Apache. Install Apache Check the status Start the process Verify the install, the Apache test page should be view able http://localhost Ensure Apache starts by default Apache configuration file Install Subversion Install the needed Apache modules subversion and mod_dav_svn Update the subversion.conf Add an entry to the "subversion.conf" file Create users, command for the first user All other users Configure the repository Create the required directories Create the repository Change ownership of repos to apache Restart Apache Test via Browser http://localhost/repos You should see "Revision 0" Creating SVN structure Verify changes using your browser http://localhost/repos SVN Clients http://tortoisesvn.net/ References: http://wiki.centos.org/HowTos/Subversion http://linuxwave.blogspot.ca/2008/02/inst...