Specially given the fact that lot of research and development has already gone into designing these wonderful tools.
This article lists 10 of such tools if you are looking for free continuous integration tools. There are other wonderful commercial tools with advanced features and to handle the development activities end to end like "AnthillPro", "AccuRev" and others which i would suggest you to go through as well apart from the free ones mentioned below.
Hudson is a continuous build and integration tool providing easy installation, configuration, change set support, permenant links to latest and successful builds, RSS/Email/IM integration, JUnit/TestNG test reporting, Distributed Builds, File FingurePrinting, PlugIns support and much more. Hundson has evolved over time and has been "the" relaible build and test product from long time and used by many.
Luntbuild is a powerful build automation and management tool. Continuous Integration or nightly builds can be easily set using a clean web interface. Executed builds are well managed using functions such as search, categorization, promotion, patching, deletion, etc. It also acts as a central build artifacts repository and download area for your whole team.
LuntBuild also comes with a commercial version which is worth exploring for enterprise purposes and seems to be much more advanced features including CI, Release Management, Issue Tracking, Build Workslfow Design, Test Insight, RESTful API and plugins support.
Written in Java and build supplied to Ant, Maven, NAnt, Phing, Rake and XCode with any other builder with commandline tool or script, CruiseControl is an extensible framework to create a custom continuous build process. It provides a web interface and is able to work with variety of source controls, build technologies, support to notifications, email, IM and by default comes with many useful plugins.
By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve.
The overall goal is to reduce tree breakage and provide a platform to run tests or code-quality checks that are too annoying or pedantic for any human to waste their time with. Developers get immediate (and potentially public) feedback about their changes, encouraging them to be more careful about testing before checking in code
Beebox acts as a continuous integration server and to manage multiple tools recognized in the market. Beebox helps to maintain a single reposiroty of source code along with automation of code compilation, complete visibility of source checkins and activities, QA automation and manage build lifecycle.
Gump can build shell script, Ant and Maven 1 projects, setting up the classpath appropriately. Ant and Maven 1 have special hooks built in them to give Gump complete control of the classpaths used to build and test the applications. This allows Gump to build the projects against the latest versions, even if the project's own build files have hard coded dependencies against static libraries in their own CVS or subversion repository.
If a build on Gump is successful, then a report is placed on the site, and all projects that declare themselves dependencies are eligible to be built. If a project fails to build, error reports are published, an error email is sent, and all dependent projects are blocked from building.
Apache Continuum is an enterprise-ready continuous integration server with features such as automated builds, release management, role-based security, and integration with popular build tools and source control management systems. Whether you have a centralized build team or want to put control of releases in the hands of developers, Continuum can help you improve quality and maintain a consistent build environment.
Draco.NET is a Windows service application designed to facilitate continuous integration. Draco.NET monitors your source code repository, automatically rebuilds your project when changes are detected and then emails you the build result along with a list of changes since the last build.
Cabie is a multi-platform, multi-cm client/server based application providing both command line and web-based access to real time build monitoring and execution information. It uses MySQL to hold build configuration and supports any build that can be activated from command line. It provides rich integration with bug tracking, and test management systems. With the idea in mind that most companies create build systems from the ground up, Cabie was designed to not have to re-write scripted builds but instead to integrate existing build scripts into a smart collector. Cabie provides rapid email notification and RSS integration to quickly handle build issues. Cabie provides the ability to run builds in parallel, series, to poll jobs or to allow the use of scripted nightly builds. Cabie is perfect for agile development in an environment that requires multiple languages and tools. Cabie supports Perforce, Subversion and CVS. The use of a backend broker allows anyone with perl skills to write support for additional CM systems.
ControlTier is an open source, cross-platform build and deployment automation framework. ControlTier can help you to coordinate and scale service management and administration activities across multiple nodes and application tiers