I just got done installing the JIRA to Subversion integration. All you need to do is to include the ticket number from JIRA in your check in comment, and JIRA will automatically link it to the issue. Here's what it looks like when looking at a JIRA issue:

Notice the WMSHARP-53 inside the comments. That's how you do it.

Thanks,

Your friendly and helpful system administrator

I finally got my copy of JIRA working through the Apache reverse proxy. We have version 5.0.2, which has all kinds of neato bug and project tracking capabilities. I've also installed a Kanban plugin called GreenHopper. I've setup anonymous read-only project access. I've also setup the ability to create issues without logging in. Our Subversion repository is now integrated with JIRA. This means that we can link check-ins with an issue or task in JIRA, by including a specific tag in the check-in comment. I'll post the exact steps in the Wiki, once I find out exactly what tags are needed. The url is http://jira.wheelmud.net

You will first see the login screen. Please look at the menu at the top of the website and click on the "Projects" menu. Here's a screenie:

CodePlex's issue tracker is very short in features, plus it makes it very tedious synchronizing check-ins with issues/tasks.

JIRA also has and IDE connector for Visual Studio. This means that we can manage issues from within Visual Studio. It's a free download over here: http://www.atlassian.com/software/ide-connectors/overview

Thanks,

Your invisible and friendly system administrator.

I fixed Apache to serve Subversion files using the HTTP protocol. You can browse the repositories through your web browsers using the folllowing link as the root: http://svn.wheelmud.net  You can use either the SVN (svn://) or HTTP (http://) protocols to access the repositories. The SVN protocol is much faster than the HTTP Subversion protocol.

Thanks,

Your invisible and friendly system administrator.

I've done a lot of System and Network stuff tonight related to our Subversion stack. We now have the ability to access our repositories with both the HTTP and SVN protocols. The HTTP protocol is working fine in the LAN, but I still have to test it through the WAN (Internet). The orginal SVN protocol access has not changed to people on the WAN, so you guys won't notice a difference.

We now have both CCNet and Jenkins running. Here's a screenshot of the two WheelMUD solutions in Jenkins:

Jenkins has a nice task scanner, that looks inside the source code for TODO comments. Here's what it looks like:

I'm currently working on getting StyleCop integrated with our build servers.

You can access Jenkins through uberSVN at http://ubersvn.wheelmud.net  I had uberSVN email everybody their passwords to this web interface.