Continuous Integration JUG Hannover
-
Upload
yann-cebron -
Category
Technology
-
view
350 -
download
0
description
Transcript of Continuous Integration JUG Hannover
ContinuousIntegration
Java User Group Hannover13.03.2013
Yann Cébron, JetBrains
Disclaimer
Diese Probleme hat bestimmt keiner jeder schon erlebt...
• You don’t have a master build script that builds everything on any machine.
• When your software doesn’t compile or pass its tests, no-one notices.
• When the code goes to QA it rarely works.
• Developer “done” means something very different from user “done”.
• The code works in development and pre-production, but not in production or test.
http://amarinda.com/articles/34_signs_continuous_integration_isnt_working
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
http://faodata.blogspot.de/2012/03/continuous-integration-best-definition.html
This Is Not A Tool
Voraussetzungen
• Agile Entwicklungsmethoden
• Mut zur Transparenz
• Wille zur Umstellung
• Lernkurve
Entwickler
• alle sind „up-to-date“
• schnelles Feedback
• Fokus
• Strukturierung
• „End-To-End“ Verantwortlichkeit aka „Done Done“
https://github.com/flinc/traffic_light
Und die anderen?
• Transparenz
• Pull statt Push
• manche vermissen vielleicht ihre erlogenen selbstdefinierten Ampeln
Release
• Dev vs. Ops
• kein „Event“
• Auswahl und Deployment eines vorhandenen Builds
• Automatisierung
Not only code…
• Dokumentation, Handbücher
• Release Notes
• System-Maintenance
Continuous Delivery
• konsequente Fortführung
• „Must-Have“ bei grossen Applikationen
• funktioniert auch in „kritischen“ Umgebungen
Vertrauen
• 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
• flickrFlipping 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
• http://www.infoq.com/presentations/Adopting-Continuous-Delivery
• http://www.infoq.com/presentations/Etsy-Deployment
• http://www.infoq.com/presentations/Facebook-Release-Process
• http://www.infoq.com/presentations/Continuous-Integration-Songkick
• http://www.infoq.com/articles/Continuous-Delivery-Maturity-Model