1. Continuous
Integration
Scrum Usergroup Hannover
26.09.2011
Yann Cébron

2. Continuous Integration is a software
development practice where members of a
team integrate their work frequently, usually
each person integrates at least daily - leading
to multiple integrations per day. Each
integration is verified by an automated build
(including test) to detect integration errors
as quickly as possible. Many teams find that
this approach leads to significantly reduced
integration problems and allows a team to
develop cohesive software more rapidly.
http://martinfowler.com/articles/continuousIntegration.html

3. Voraussetzungen
• Agile Entwicklungsmethoden
• Mut zur Transparenz
• Wille zur Umstellung

4. Entwickler
• alle sind „up-to-date“
• schnelles Feedback
• Fokus
• Strukturierung

5. Und die anderen?
• Transparenz
• Pull statt Push
• (und keine Fake-Ampeln mehr)

6. Release
• kein „Event“
• Auswahl und Deployment eines
vorhandenen Builds
• Automatisierung

7. Not only code…
• Dokumentation, Handbücher
• Release Notes
• System-Maintenance

8. Continuous Delivery
• konsequente Fortführung
• „Must-Have“ bei grossen Applikationen
• funktioniert auch in „kritischen“
Umgebungen

9. Vertrauen

10. • Continuous Integration (Martin Fowler)
http://martinfowler.com/articles/continuousIntegration.html
• 10 Deploys Per Day (flickr)
http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-
ops-cooperation-at-flickr
• flickr
Flipping Out (flickr) http://code.flickr.com/blog/2009/12/02/
flipping-out/
• http://www.continuousdelivery.com/
http://www.slideshare.net/jezhumble/continuous-
delivery-5359386
• http://amarinda.com/articles/
34_signs_continuous_integration_isnt_working