Now that I can focus on more application development issues at work, it is time to start bringing up some of the open source life-cycle tools I need. Integrating the individual tools (MediaWiki, Bugzilla, Subversion, Mailman, WordPress, etc..) requires some work. This has proven to be a little different than my previous experience because we are an Active Directory shop. MS Active Directory actually uses a form of LDAP for authentication but it is different enough that each of the tools I use requires a little… playing… to get it working. Here are the important links:
- –MediaWiki LDAP Authentication — Contains AD specific information in it’s section on configuration.
- –MediaWiki WordPress Integration — Specific information on getting the very best wiki software and the best available blogging software talking to each other.
- –Bugzilla/SVN/MediaWiki/Mailman Integration — A walk-though on getting magic identifiers on four of the most useful application development tools available. This functionally links Subversion, Bugzilla, MediaWiki, Mailman, ViewCV, Apache, MySQL, svnmailer, svn2cl, and Bonsai. I know of very few organizations that have such a complete set of development life-cycle tools. In addition you can add code auditing (via Codestriker), source tree monitoring (via Tinkderbox), automated developer/project statistics (via StatSVN), source code indexing (with LXR), and the list just goes on.
- –MediaWiki Active Directory Integration — This is a forum post that I found useful in the AD process with MediaWiki.
- –Bugzilla Option Additional Configuration — A subsection of The Bugzilla Guide. Provides support on setting up LDAP, patch viewing, persistent bug whining, dependency charts, and incident graphs.
- –Integrating Bugzilla with Active Directory — THE setup information to get Bugzilla working with an Active Directory Tree.
- –Scmbug Homepage — Scmbug is a tool to integrate software configuration management tools with bug tracking software (i.e. it connects tools like CVS and Subversion, with tools like Bugzilla and Mantis.)
- –Subversion and Bugzilla integration with BugTraq and Scmbug — An example configuration by Platinum Solutions combining those four tools.
- –WebSVN: Subversion repository broswer — Another Platinum Solutions document talking about WebSVN. WebSVN allows for web based browsing of repository data. It is different from a tool like ViewCV in that it supports Subversion authorization. WebSVN is not as advanced a tool as ViewCV but it’s native subversion authentication makes it a good fit in some places.
- –Bugzilla accounts in Subversion with mod_auth_mysql — Platinum Solutions has another great article on setting up shared users between Bugzilla and Subversion. This is much easier then configuring my setup with Active Directory authentication.
The reality is that if you company is not doing re-time build tests, nightly builds, automated testing, bug tracking with integration into you source control management system, and automated reporting; then your company is waisting developers time and resources. Open Source has only been as successful as it has because of the plethora of automated tools available to them. Your competition is using them… you better be. There are hundreds of freely available software engineering tools in the Open Source world. Check out Tigris.org for a fairly complete list.
I too am beginning work on a similar effort. I am looking to do something very similar to you, except my personal preference is for Mantis instead of Bugzilla.