Continuous Integration JUG Hannover

370 views

Published on

Vortrag vom 13.03.2013

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
370
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Continuous Integration JUG Hannover

  1. 1. ContinuousIntegrationJava User Group Hannover 13.03.2013 Yann Cébron, JetBrains
  2. 2. Disclaimer
  3. 3. 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
  4. 4. 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
  5. 5. http://faodata.blogspot.de/2012/03/continuous-integration-best-definition.html
  6. 6. This Is Not A Tool
  7. 7. Voraussetzungen• Agile Entwicklungsmethoden• Mut zur Transparenz• Wille zur Umstellung• Lernkurve
  8. 8. Entwickler• alle sind „up-to-date“• schnelles Feedback• Fokus• Strukturierung• „End-To-End“ Verantwortlichkeit aka „Done Done“
  9. 9. https://github.com/flinc/traffic_light
  10. 10. http://www.youbrokethebuild.com/
  11. 11. Und die anderen?• Transparenz• Pull statt Push• manche vermissen vielleicht ihre erlogenen selbstdefinierten Ampeln
  12. 12. Release• Dev vs. Ops• kein „Event“• Auswahl und Deployment eines vorhandenen Builds• Automatisierung
  13. 13. Not only code…• Dokumentation, Handbücher• Release Notes• System-Maintenance
  14. 14. Continuous Delivery• konsequente Fortführung• „Must-Have“ bei grossen Applikationen• funktioniert auch in „kritischen“ Umgebungen
  15. 15. Vertrauen
  16. 16. • 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
  17. 17. • 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

×