FogBugz 5 + Subversion + Multiple Repositories + WebSVN + Ruby = Good Times

Well... in a nerdy sort of way I guess.

A couple of months ago our IS department switched from a quasi-homegrown case/bug tracker to FogBugz 5. Although we use it mainly as a way to track end-user support requests, one of the biggest things I wanted was a good bug tracking system for our in-house developed software that would tie into our Subversion repositories.

It took me a while to find the time to sit down and get it going, but finally as of today I have FogBugz talking to multiple Subversion repositories and using WebSVN to display changed file and diff information. Turns out that it wasn't as easy as I thought it would be.

Attaching FogBugz to a single Subversion repository is a slam dunk right out of the box, but multiple repositories wasn't so crystal clear. Turns out others have fought with this in the past as well. A quick search on the FogBugz Technical Support Forum turns up a few threads with people looking for answers and others offering suggestions.

I start out with this page on the Fog Creek web site about setting up multiple repositories which gives a nice for an overview of how it works. Then this post on the tech support forum which has a link to a .zip archive containing a modified version of the repo.asp file referenced on the Fog Creek page.

I got that version of the repo.asp configured and in place on our FogBugz server and installed WebSVN 2.0RC4 on the Linux server that also houses our Subversion repositories. The next step was actually getting information into FogBugz when committing changes.

This is where I really went off the normal track I guess. Accidentally I wrote a Ruby script that would run post-commit... accidentally just in that I was attempting to understand it all better and can get a script up and going quicker in Ruby right now.

My script differs from the scripts supplied in that there is one file... a Ruby script called post-commit which is placed the in the hooks directory of all the Subversion repositories. This handles everything instead of having one post-commit file that calls logBugDataSVN.pl.

So here's the Ruby script as it is today. I've still got to test a few more things to make sure all is well but as of right now it has been working for a few days here. Feel free to e-mail me with questions.