Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Spot defects early with Continuous Integration

Your complete guide to creating a best-of-breed CI environment

Andrew Glover (aglover@stelligent.com), President, Stelligent Incorporated
Andrew Glover is president of Stelligent Incorporated, which helps companies address software quality with effective developer testing strategies and continuous integration techniques that enable teams to monitor code quality early and often. Check out Andy's blog for a list of his published work.

Summary:  Continuous Integration (or CI) is a process that consists of continuously compiling, testing, inspecting, and deploying source code. In many Continuous Integration environments, this means running a new build anytime code within a source code management repository changes. The benefit of CI is simple: assembling software often greatly increases the likelihood that you will spot defects early, when they still are relatively manageable. In this tutorial, a companion to his series In pursuit of code quality , Andrew Glover introduces the fundamental aspects of Continuous Integration and steps you through how to set up a CI process using best-of-breed open source technologies.

Date:  20 Nov 2007
Level:  Intermediate PDF:  A4 and Letter (1590 KB | 43 pages)Get Adobe® Reader®

Activity:  28389 views
Comments:  

Before you start

Learn what to expect from this tutorial and how to get the most out of it.

About this tutorial

This tutorial discusses the fundamental aspects of Continuous Integration: what it is, why you need it, how it works, even the pace of development in a CI environment. It shows you how to set up a CI process that delivers a repeatable and reliable build process.

You'll learn how to properly configure a CI server to poll an SCM repository and run an Ant build process anytime a change is detected in your source code. You'll also learn how to run automated JUnit tests and how to make the most of both PMD and FindBugs for software inspection. Finally, you'll see for yourself how Hudson, truly a best-of-breed CI server, informs you of issues as they arise, ultimately enabling you to build reliable software more quickly.


Objectives

This tutorial guides you step-by-step through the fundamental concepts of Continuous Integration using Hudson, Ant, and Subversion as your framework. When you are done with this one-hour tutorial, you will understand the benefits of Continuous Integration as well as how to set up and properly configure Hudson, Ant, and Subversion to work together. The resulting build process will run both tests and software inspections and will report back violations almost as quickly as they occur.


Prerequisites

To get the most from this tutorial, you should be familiar with Java™ development in general. This tutorial also assumes that you understand the value of building software with an acceptable level of quality and that you are familiar with JUnit.


System requirements

A Continuous Integration environment requires an automated build tool, a code repository, and a CI server. To follow along and try out the code for this tutorial, you'll need a working installation of the Java platform as well as Hudson 1.150, Ant 1.7, JUnit 3.8.1, and Subversion 1.4.x.

The recommended system configuration for this tutorial is as follows:

  • A system supporting either the Sun JDK 1.5.0_09 (or later) or the IBM Developer Kit forJava technology 1.5.0 SR3 with at least 500 MB of main memory
  • At least 20MB of disk space to install the software components and examples covered

The instructions in the tutorial are based on a Microsoft® Windows® operating system. All the tools covered in the tutorial also work on Linux® and Unix® systems.

1 of 14 | Next

Comments



Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Java technology
ArticleID=269591
TutorialTitle=Spot defects early with Continuous Integration
publish-date=11202007
author1-email=aglover@stelligent.com
author1-email-cc=

Tags

Help
Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere).

My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).

Use the search field to find all types of content in My developerWorks with that tag. Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere). My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).