This document introduces continuous integration, which aims to build, test, and release software faster through practices like automating builds and tests. It recommends releasing software early and often, as well as setting up an automated deployment pipeline with build, test, and build server steps. Continuous integration helps reduce stress during releases by catching bugs early and breaking code frequently in a controlled way.

1. Introduction to
Continuous Integration
How I Learned to Stop Worrying and Love
the Bugs

3. Linked Senior

4. “early and continuous delivery of
valuable software”
-- Agile Manifesto
“Release early, release often”
-- Eric Raymond

5. Super Star Developer

6. Stressful Releases

7. Sudden Clarity

8. Deployment Pipeline

9. Step 1: Automate Build
$ compile *.*
$ zip myapp.zip
$ scp_upload myapp.zip

10. Step 2: Automate Tests
Watir
create_user(username, password)
user = login(username, password)
assert user != null

11. Less Stressful Releases

12. When should we run tests?
1. Before release
2. Before demo
3. When you have
time
4. Every week
5. Every day
6. Other

13. Step 3: Build Server

14. Jenkins Demo!

15. Continuous Integration
“A set of practices and principles
aimed at, building, testing, and
releasing software faster and more
frequently”
-- Unknown

16. Break Things

17. Thank You!
Herve Vu Roussel
hroussel@gmail.com
http://linkedin.com/in/hroussel