Continuous Integration Brown Bag

Continuous
Integration
Brown Bag by Clarence Bakirtzidis
18th June 2013
Wednesday, 19 June 13

Overview
What is CI?
Beneﬁts of CI
How to start doing CI
Live Demo
Tips for Success

What is CI?
Continuous Integration = CI
"The aim of Continuous Integration is that the
software is in a working state all the time" [1]
What type of “software” are we talking about?
CI helps avoid “integration hell”
“Bring the pain forward”
[1] Continuous Delivery (book), Jez Humble & David Farley

What is CI? [cont.]
With CI: Your software is proven to work with
every change (assuming sufﬁciently
comprehensive automated test suite)
Without CI: Your software is broken until
someone proves it works, usually during a
testing or (typically late) integration stage

Beneﬁts of CI
Reduced integration time and cost
Reduced delivery risks
Improved and shorter feedback cycles
Improved team communication
Improved software quality

Beneﬁts of CI [cont.]
Having a comprehensive automated test suite
supports TDD (fast feedback) and refactoring
Early warning system for issues
Visibility of the health and production
readiness of the software outside of the team

Feedback / Radiators
Image Sources:
#1: http://www.ﬂickr.com/photos/hanuska/5931613961/in/photostream/
#2: http://fabiopereira.me/blog/wp-content/uploads/2009/12/cibuildlightvscidashboardradiator.png

Pre-requisites: Version Control, Automated
Build, Agreement of the team, CI Server
(optional but highly recommended)
Start simple - automate build, add some
automated tests, incremental improvements
Make sure everyone understands the CI
process, scripts and how to run them

Put everything required to build and test your
software in source control
Start building a CI server to run your build,
tests, package, etc, on every commit
Advanced CI: Build and Test Everything: Code
+ Conﬁguration + Infrastructure changes
Typical day-to-day Developer CI scenario...

Develop
Local
Workstation

Build
Develop
Local
Workstation

Mainline Server
Build
Develop
Local
Workstation

Mainline Server
Build
pull
Develop
Local
Workstation

Mainline Server
Build
Build
pull
Develop
Local
Workstation

Mainline Server
Build
Build
pull
Develop
Local
Workstation
push

Mainline Server
Build
Build
pull
Develop
Local
Workstation
Build
push

Mainline Server
Build
Build
pull
Develop
Local
Workstation
Build
push
✔
Done!

CI Stages
Images from “Continuous Delivery” (book) by Jez Humble &
David Farley

CI Stages
Commit stage
Compile
Unit test
Assemble
Code analysis
source code
commit tests
build scripts
deployable binaries
test reports
metadata
Version
control
Artifact
repository
Acceptance test stage
Conﬁgure environment
Deploy and smoke test
Acceptance test
Tear down
acceptance tests
deployment scripts
conﬁguration data test reports
metadata
Version
control
Artifact
repository
binaries
Artifact
repository
Images from “Continuous Delivery” (book) by Jez Humble &
David Farley

Manual Stages
Image from “Continuous Delivery” (book) by Jez Humble &
David Farley

Manual Stages
Later stages
Conﬁgure environment
Deploy and smoke test
Tear down on request
deployment scripts
conﬁguration data
test reports
metadata
Version
control
Artifact
repository
binaries
Artifact
repository
Image from “Continuous Delivery” (book) by Jez Humble &
David Farley

But what about...
Scheduled builds vs. build on every commit?
Branching vs Mainline: Good or Evil?
Changes that are not ready for use?
Off-the-shelf packages?
Distributed teams?
Large projects?

P1 P2
G2 G3G1 G4
P3 P4 P5
G5 G6
B1 B2
G1
G1
P1
P1
B1
P2
B1
P1-2
G2
G2
P3
G2
P3
B2
P4
B2
G3
P3 G3
G3
P4
P4 P5
P4-5
G4
G4 G5 G6
P2
Professor Plum
Reverend Green
Mainline
Continuous Integration

P1 P2
G2 G3G1 G4
P3 P4 P5
G5 G6
B1 B2
G1
G1
P1
P1
B1
P2
B1
P1-2
G2
G2
P3
G2
P3
B2
P4
B2
G3
P3 G3
G3
P4
P4 P5
P4-5
G4
G4 G5 G6
P2
Professor Plum
Reverend Green
Mainline
P1 P2
G2G1
B1
B1
B1
P1-2
G1-2
G3 G4
P4
B2
P5
G5 G6
B2
P3-4
G3
B2
P3
Professor Plum
Reverend Green
Mainline
G1-6
P1-5
P1-5
G1-6
Feature Branch

Feature Branch

Feature
Branch

Feature
Branch
Release
Branch

Feature
Branch
Release
Branch
Experimental
Branch

Live Demo
LOADING, PLEASE WAIT...

Tips for Success
Checkin regularly - Everyone commits to the
mainline every day
Create a comprehensive automated test suite
Keep the commit stage fast
Make the build visible (dashboards, build
lights)
Automate the build (run it on a CI server)

Tips for Success
[cont.]
Agree on build hygiene and responsibilities
Don't checkin on a broken build
Take responsibility for all breakages that result
from your changes
Every commit to mainline should be
automatically tested
Don't comment out failing tests

References
Martin Fowler
http://www.martinfowler.com/articles/continuousIntegration.html
Continuous Delivery
Chapter 3 - Continuous Integration, Jez Humble and David Farley, C.
2011 Pearson Education, Inc.
Wikipedia
http://en.wikipedia.org/wiki/Continuous_integration

Next Steps
Books
Continuous Delivery, Jez Humble & David Farley
Continuous Integration, Paul M. Duvall
Internet Resources
"Continuous Integration is an Attitude, Not a Tool" (http://
www.jamesshore.com/Blog/Continuous-Integration-is-an-
Attitude.html)

Questions?
Clarence Bakirtzidis
Twitter: @clarenceb_oz
Email: clarenceb@gmail.com

Credits
Slides 10, 14, 15, 16 - Tom Sulston
(@tomsulston), ThoughtWorks, from his
presentation
Slides 11, 12 - Images are from the
“Continuous Delivery” book by Jez Humble &
David Farely
Other photo credits are indicated on the slides
where they are used

Continuous Integration Brown Bag

Recomendados

Recomendados

Más contenido relacionado

Similar a Continuous Integration Brown Bag

Similar a Continuous Integration Brown Bag (20)

Último

Último (20)

Continuous Integration Brown Bag