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...

While you can set Hudson/Jenkins to poll SVN at specific times an alternative is to let SVN inform Hudson when a new change has been committed to the repository. Requirements: You will need access to the server that hosts your SVN repository. You have a project setup and configured in Hudson. Adding the SVN Plugin The following Hudson plugin is installed, version 1.20 for this example. From the Hudson Console: Click Manage Hudson-Manage Plugins Ensure the Subversion Plugin is added. Adding the SVN Hook to SVN Once the plugin has been added its time to update the SVN hook. Using a text editor, VM or VIM edit the "post-commit" file in your SVN repository hooks directory. An example based on the "Oracle Virutal Developer Days VM" Repository directory: /home/oracle/labs/Dev_labs/svn_repos/otnvdd/hooks File: post-commit An sample "post-commit" file: Verify your changes: Once you have the SVN hook in place, its time to make a change ...

As part of getting some new members up to speed I needed create an SVN repository for project related check-in. I decided to go with Apache SVN which is easy to setup on Apache. Installation the following software Apache HTTP Server 2.2.1 http://httpd.apache.org/ Apache Subverion - 1.7.1 Win32Svn (32-bit client, server and bindings, MSI and ZIPs; maintained by David Darj) http://subversion.apache.org/packages.html Reboot to ensure paths are set correctly Apache Installation note Using port 80 it should install as a service to ensure SVN is active on restart Creating a repository on the Server Copy required modules Copy the files mod_authz_svn.so and mod_dav_svn.so Configure Apache httpd.conf In the modules section ensure the following setting exist Create and add user(s) to the authfile Connect and Confirm using IE, Chrome or FireFox Setting up the standard directories Checkout the repository using TortiseSVN or a command line tool Create the follow...