Continuous Integration

A simple presentation to all developers in my company. Let them know why we introduce the CI to our agile development cycle.

Transcript

1. CI Scribe Huang @scribetw
2. What is CI?
3. Continuous Integration
4. Commit Analysis Test Build Report
6. Why we use CI?
7. •Automation •Standard Environment •Release early. Release often.
8. The Four Circles of XP Source: http://blogs.msdn.com/b/jmeier/archive/2010/04/04/the-four-circles-of-xp-extreme-programming.aspx
9. The Four Circles of XP Source: http://blogs.msdn.com/b/jmeier/archive/2010/04/04/the-four-circles-of-xp-extreme-programming.aspx
10. How to use CI?
11. 0. Find a solution
12. Free edition available >>
13. 1. Create a job
14. Fetch source repository
15. Build tool script
16. Automatic unit tests Spock Framework *Icon source: http://habrahabr.ru/post/137561/
17. Code coverage report JMockit Coverage
18. 2. Just commit it
19. 3. View report
22. 4. Fix the problems and commit it
23. 5. View report (again!)
25. 6. …? You knew that. More commit!
26. Demo Time! http://10.3.0.127/
27. Thank you! Questions?
28. • Github icon: – Hand Drawn Goods – handdrawngoods.com – Creative Commons (Attribution 3.0 Unported) • Server icons: – PICOL - http://www.picol.org – Creative Commons (Attribution-Share Alike 3.0 Unported) • Trademarks: – All trademarks remain property of their respective holders, and are used only to directly describe the products being provided.