 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
Presenter
Background
Continuous Integration, CI, is a very important best practice - especially in XP. CI means that you always integrate as soon as possible to a working product. It is very helpful to automate CI. If the team always has a working build to deliver, it can adapt to changes much quicker. A working CI set-up should include automated builds of deployment kits, e g a working install kits on a CD master file. The team should always have an installable product available that has passed all of its acceptance tests.
Summary
This tutorial teaches down-to-earth techniques and best practices to make Continuous Integration work in your environment: How to start easy with manual integration at a Single Point of Release. Practices with version control systems that help you automate build cycles. Why we include the deployment kit in CI. Automating Install kit generation. How to integrate your builds with other projects. How to make target environment testing more predictable, automated and get rid of hard disk copying to reset the target environment to a virgin state.
The tutorial includes techniques and tactics for configuration management/version control in XP, that are based of recent research at Lund University, Sweden
Erik shares his experiences and techniques from helping several XP teams build their very own flavour of CI system.
This tutorial will give practical advice for people, interested in people and technology, on how to build a working Continuous Integration system, from common parts.
Tutorial format
Half Day
Prerequisites
The participants should have some experience in software development and a keen interest in making better, greater products by working on the success of a team.
Content
-
Aiming for Continuous Integration, CI
-
Starting out with Single Point of Release
-
Full cycle from code check-in to automated acceptance test in target environment of installed build
-
Setting up configuration management/version control for CI
-
Version control/CM best practices that help you automate CI.
-
Popular tools for CI automation
-
CVS, SourceSafe and the usual suspects.
-
A closer look at Thoughtworks freeware CruiseControl – a CI build robot.
-
A practical setup with CVS and Cruisecontrol
-
Automated builds of install kits
-
Automated deployment in target environments
-
Automated testing in target environments
-
Building a CI server machine including target environments
-
How-to use VMWare to build effective target environments that are virgin at each boot
-
Automating VMWare workstation as part of your CI server.
-
Demo of a full working CI system from check-in to automated acceptance test in target environment, "built from household items".
Erik Lundh
Erik has recently helped XP teams build their CI systems in both small and large companies, some in a few of Europe’s largest companies with a stake in software development.
Erik Lundh has 20 years of experience of product oriented software development. He chose XP as the preferred process in an effort to create a cross-industrial center of excellence, developing usable and safe software. Erik is an independent who spend time as mentor and coach at companies that develop software for products. He serves as an advisor to management and as a director at the board of selected companies. Erik is very active in both the regional SPIN-SYD for the south of Sweden and the national SPIN-SWEDEN. Erik has initiated international exchanges e g with SPIN in Bangalore, India.
Erik currently acts as coach to several XP-teams working with product-oriented software development.
Erik promotes XP in Sweden through conferences, newsletters and coaching. Erik has recently appeared in high profile XP panels with Kent beck, Ron Jeffreis et al, at XP2002 and OOPSLA 2002.
Supporting material
XP – The Addison Wesley XP series
Thoughtworks CruiseControl
VMWare