More Related Content
![[Quang nguyen] Continuous Integration XP Day 2015 Vietnam Danang](https://cdn.slidesharecdn.com/ss_thumbnails/quangnguyencontinuousintegrationxpday2015danangquangnguyen-150520014341-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
Continuous integration
- 1. Continuous Integration with myfriends from Middle Earth
- 2.
- 3.
- 4. Continuous Integration • Whatis it? • Why we do it? • How do we do it?
- 5. “good luck withthat”
- 6.
- 7. “Continuous integration (CI)is the practice, in software engineering, of merging all developer workspaces with a shared mainline several times a day.” http://en.wikipedia.org/wiki/Continuous_integration
- 8. It’s a bitlike Agile • It’s a set of 10 principles • Principles describe techniques • There are tools to help you do it • But noone started a war over CI (yet)
- 9. • Maintain acode repository • Automate the build • Make the build self testing • Everyone commits to the baseline every day
- 10. • Every commit(to baseline) should be built • Keep the build fast • Test in a clone of the production environment • Make it easy to get the latest deliverables
- 11. • Everyone cansee the results of the latest build. • Automate Deployment.
- 12. Why do wedo it?
- 13. http://en.wikipedia.org/wiki/Continuous_integration ...to prevent integrationproblems, referred to as "integration hell"
- 14.
- 15.
- 16. How development teams seethemselves
- 17. How development teams seethemselves
- 18.
- 19.
- 20. “Computers can performalmost any conceivable action faster than a human” Jamie Wiseman
- 21. • Time todeploy • Testing time • Hotfixes
- 22.
- 23.
- 24. • PEBKAC (typlingfail) • Technical Debt • Rollback • Timings • Not noticing!
- 27. How do wedo it?
- 28. Tools • Git repositories(gitlab, github, bitbucket, gitorious, etc) • Jenkins • Fabric • IRC
- 34. Testing • Simpletest • PHPUnit •Selenium • Behat/Mink/XVFB
- 35.
Editor's Notes
- #3 Hello. Welcome.
- #4 Who am I (I use grown up language sometimes) What Code Enigma do What I do with Code Enigma Probably going to talk a bit about how these slides were made, very excited by them
- #5 re: How - wanted to do a live walkthrough, unprepared
- #6 Originally wanted to do a live walkthrough, no internet access. You’re all left with a crappy slideshow.
- #9 So things we SHOULD do, things we ACTUALLY do things we ACTUALLY do this WITH
- #10 What I like to call ‘filler’ slides.
- #11 Arguably, you should DEVELOP in a clone of the production environment. Actually, no it’s not arguable. Just do it. Save yourself time and pain.
- #12 You can tell I discovered the ‘build in’ options here.
- #15 What was release day? What was release day *like*? Stressful. Time consuming. Risk. (looking back, it was quite fun, but not for right reasons)
- #23 Time = Money How long does it take to build stuff?
- #24 Types of risk, and how they’re mitigated with CI tools