0
ContinuousIntegrationScrum Usergroup Hannover       26.09.2011      Yann Cébron
Continuous Integration is a softwaredevelopment practice where members of ateam integrate their work frequently, usuallyea...
Voraussetzungen• Agile Entwicklungsmethoden• Mut zur Transparenz• Wille zur Umstellung
Entwickler• alle sind „up-to-date“• schnelles Feedback• Fokus• Strukturierung
Und die anderen?• Transparenz• Pull statt Push• (und keine Fake-Ampeln mehr)
Release• 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“  Um...
Vertrauen
•   Continuous Integration (Martin Fowler)    http://martinfowler.com/articles/continuousIntegration.html•   10 Deploys Pe...
Upcoming SlideShare
Loading in...5
×

Continuous Integration - Scrum Usergroup Hannover

476

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
476
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Continuous Integration - Scrum Usergroup Hannover"

  1. 1. ContinuousIntegrationScrum Usergroup Hannover 26.09.2011 Yann Cébron
  2. 2. Continuous Integration is a softwaredevelopment practice where members of ateam integrate their work frequently, usuallyeach person integrates at least daily - leadingto multiple integrations per day. Eachintegration is verified by an automated build(including test) to detect integration errorsas quickly as possible. Many teams find thatthis approach leads to significantly reducedintegration problems and allows a team todevelop cohesive software more rapidly. http://martinfowler.com/articles/continuousIntegration.html
  3. 3. Voraussetzungen• Agile Entwicklungsmethoden• Mut zur Transparenz• Wille zur Umstellung
  4. 4. Entwickler• alle sind „up-to-date“• schnelles Feedback• Fokus• Strukturierung
  5. 5. Und die anderen?• Transparenz• Pull statt Push• (und keine Fake-Ampeln mehr)
  6. 6. Release• kein „Event“• Auswahl und Deployment eines vorhandenen Builds• Automatisierung
  7. 7. Not only code…• Dokumentation, Handbücher• Release Notes• System-Maintenance
  8. 8. Continuous Delivery• konsequente Fortführung• „Must-Have“ bei grossen Applikationen• funktioniert auch in „kritischen“ Umgebungen
  9. 9. Vertrauen
  10. 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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×