1.
Who let the robot out?
Building high quality software
with Continuous Integration
Timo Stollenwerk

2.
Wishful Thinking
In Time
In Budget
Bug Free
Readable Code
Maintainable Code
Documented
Fast
Working

3.
Real Life
Broken build
It works on my machine
Not deployable
Bad performance
Unmaintainable code
Over time
Over budget

4.
Assumption is the mother of all screw-ups

5.
Software Quality?!

6.
Basic Ideas

7.
Do not break things

8.
If things are broken, don't make it more complicated

9.
If you broke the build, fix it as soon as possible

10.
Getting Started
Post-commit hook
Failure / Fix

11.
Tests
collective.xmltestreport / Jenkins Cobertura Plugin

12.
Acceptance Tests
Robot
Framework
Jenkins Robot Plugin / Saucelabs

13.
Code Analysis
buildout.jenkins / plone.recipe.codeanalysis / Jenkins Violations Plugin

14.
Performance Tests
Jenkins jMeter Plugin

15.
Documentation
Sphinx / Robot / Build Step

16.
Notifications
Jenkins Ext-Email Plugin / Jenkins Dashboard Plugin

17.
Continuous Deyploment
Jenkins Build Pipeline Plugin

18.
What do we get?
In Time
In Budget
Bug Free
Readable Code
Maintainable Code
Documented
Fast
Working

19.
Who let the robot out?
Timo Stollenwerk
IRC: tisto
tisto@plone.org
Building high quality software
with Continuous Integration

20.
●
Robot: http://www.flickr.com/photos/jerry_reynolds/2538180907
●
Dark Sky: http://www.flickr.com/photos/psychoscheiko/5812349452
●
Lego: http://www.flickr.com/photos/ogimogi/2253657555
●
Broken Glass: http://www.flickr.com/photos/akeg/2230862848
Image Credits