Feb
12
Written by:
admin
Monday, February 12, 2007
I have taken the last few days to setup and implement Continuous Integration for the BugNET project. For those who are not familiar with this process please refer to this good article by Martin Fowler.
I am a big fan of this process and we have been using it where I work for sometime now. Setting it up for this project is part of my plan to shorten the release cycles and put some structure behind the development process. By implementing continuous integration and cruisecontrol.net there will always be deployable build and source packages, unit tested, documented and ready to go after each code check-in. Unfortunately these builds will not be made public at this time because cruisecontrol.net running on a local machine.
The other part of shortening release cycles will be to tackle less number of enhancements per version. One or maybe two major enhancements and other bug fixes per release are the goal so expect the version numbers to climb fast.
If you haven't already set up continuous integration for your projects I urge you to immediately. The benefits to this process are countless.
Keep watch for more news!
Tags:
Re: BugNET Goes Continuous!
It would be really cool if you documented how you implemented this process. It sounds interesting and I'd like to do it on some of my projects as well, but I don't know where to begin.
By jensenkd on
Tuesday, February 13, 2007
|
Re: BugNET Goes Continuous!
The reason I didn't go into detail is because it is very popular right now and a wealth of information out there on the topic. Search google and you will find some good articles on how to get started.
By admin on
Tuesday, February 13, 2007
|
Re: BugNET Goes Continuous!
Yeah...good idea! Keep it continuously integrated! ;)
By rachitpatel on
Wednesday, February 28, 2007
|