SCMWise.com

Continuous Integration


CI Definition

Continuous Integration, CI, is the process of building your application on every new source code check-in.

Although, considered a relatively new idea, the concept behind CI has been around for as long as development teams have been writing code.

The long standing problem for software development teams have been the integration of the new code and the stability of the application.

The integration would be so painful that many development teams would put off integration until they thought they were code complete.

The problem with that particular idea was no one could accurately predict how long it would take to complete the integration.

In some cases, the integration could take as long as the coding for a new release.


The benefits of CI

  • Instant build feedback
  • Reduced risk of code instability
  • Easier and quicker bug detection and removal
  • Allows for more deployments for testers and end-users



CruiseControl

CruiseControl for Continuous Integration is a software build framework for continuous build processes.

It includes integration with many other build tools and various source control tools.

A gui interface is provided to view the details of the current and previous builds.

CruiseControl is distributed under a BSD-style license and is free for use.

CruiseControl is an open source tool. Therefore, it makes the source code freely available.


Build Automation and CI

Build Automation is the key to implementing a successful Continuous Integration.

For more information about Build Automation


Software Build Tools

There are many Software Build Tools used to create and automate software builds.

This list of Software Build tools is growing and the functionality of the tools is expanding.

These tools have come along way in standardizing and simplifying the SCM Engineer's life in regarding to the automation of the software build.

Visit our List of Software Build Tools


CI and Build Best Practices

CI is one of many Software Engineering Best Practices.

Following Software Build Best Practices helps ensure that your development environment is always in a state to build.

For more information about Build Best Practices


Software Build Tool Reviews

We need your Build Tool Reviews.

If you build software and have built a CI environment we would like to hear from you:

Software Build Tool Reviews



Software Build Table of Contents

Software Build Build automation is the process of combining all the steps necessary to compile the source code into build artifacts into a one step process. This can include many different types of tasks depending on the technologies involved.

Agile Continuous Integration Agile Continuous Integration naturally supports the Agile Development process of small and frequent releases. Continuous Integration, CI, is the process of building your application on every new source code check-in. Although, considered a relatively new idea, the concept behind CI has been around for as long as development teams have been writing code.

Automated Builds Automated Build Process - Automating your software build process is a fundamental step in maturing your software development process. The only way to accurately predict build results, ensure build reproducibility and guarantee minimal development down time due to build issues is to fully automate the build process.

Build Automation Build Automation is the key to implementing a successful Agile development methodology. In its basic form The Build is the conversion of source code into binaries. However, there is much more to building software than just compiling code.

Build Management Build Management is the process of assembling all the components of a software application into an installable software product. For development teams looking to increase efficiencies and improve quality of their software, one of the most important places focus is the software build process.

Continuous Integration Continuous Integration, CI, is the process of building your application on every new source code check in. Although, considered a relatively new idea, the concept behind CI has been around for as long as development teams have been writing code. CI is an integral part of Software Configuration Management, SCM.

CruiseControl CruiseControl is an open source tool setup specifically to perform continuous integration software builds. This page is high level overview of CC and its functionality and benefits. Software build tools like CC are an integral part of your Software Configuration Management System.

CruiseControl.Net CruiseControl.Net is an open source tool that facilitates the integration of software builds. This page is an overview of the CC.Net Tool and Process.

Maven Maven is a tool that can now be used for building and managing any Java-based project.

Software Build Best Practices Software Build Best Practices are the procedures and processes that ensure software build integrity, repeatability and reproducibility. Best Practices are practices and techniques that are the most effective way of ensuring repeatability of a process. Build Best Practices are an integral part of Software Configuration Management, SCM.



SCMWise Configuration Spec



© Copyright 2007 - 2017
Powered by Site Build It!
Page copy protected against web site content infringement by Copyscape SCMWise.com's Privacy Policy
ADD TO YOUR SOCIAL BOOKMARKS: add to BlinkBlink add to Del.icio.usDel.icio.us add to DiggDigg
add to FurlFurl add to GoogleGoogle add to SimpySimpy add to SpurlSpurl Bookmark at TechnoratiTechnorati add to YahooY! MyWeb