Continuous Integration

These days, more and more companies are adopting continuous integration strategy for developing software applications. Continuous integration involves, putting a build server to build your projects periodically.

• In this way, builds can be automated
• Even clients can track the progress of the project and have a preview of the project by using the latest builds.
• This helps the clients to track the progress of the project.

Continuous integration prevents any last minute hassles in a project. When ever some code is changed, if there is some problem, it breaks the build and a warning regarding the incompatible code can be obtained.

However, you need to put a dedicated build server for implementing Continuous Integration.

Some tools that you can use to implement Continuous integration. See more details about Continuous integration here - at Martin Fowler's site. http://www.martinfowler.com/articles/continuousIntegration.html

• Cruise Control - a SourceForge hosted framework for a continuous build process
• Tinderbox - a Mozilla based product
• Luntbuild, another SourceForge hosted framework, claims to be a Build Management tool