One of the problems with agile team development is having a server that is updated as constantly as the code is. Sure an SVN helps solve the issue of keeping everyones local code up to date as they need it but there has been no easy way to keep a centralized server updated that both all(all being the client and scrum master) can see.

But if there was a server that was constantly updated with the latest code it would help build transparency between the agile development team and the client. Also it allows the team to constantly make sure that the code not only works locally but also on the server.

The Solution: CruiseControl.rb

I setup CruiseControl today for the first time. I have done some research and looked through several tools for continuous integration of Ruby on Rails. After doing the research and reading some reviews I decided the tool we should utilize for our agile development team was CruiseControl.rb.

The installation was relatively easy.

1. Download CruiseControl.rb
2. Add the Project(s) to CruiseControl
3. Run the Start Command

Now those are the 3 easy steps that CruiseControl claims it takes to setup. This will get the basic continuous integration running. Of course I had to customize my installation of CruiseControl. I setup emailers so the team would all receive emails about every build that is pushed which included whether the build passes or fails. I still have more to learn about CruiseControl and look forward to customizing it further.

Conclusion

Although this solution is not a perfect one, it will grow and get better as we learn more about CruiseControl and customize it for our needs. Until we find something better CruiseControl will keep our programs rolling down the highway of development.