Continuous Integration: Blueprint, Toolbox, Master Craft
The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (7)
Ähnlich wie Continuous Integration: Blueprint, Toolbox, Master Craft
Ähnlich wie Continuous Integration: Blueprint, Toolbox, Master Craft (20)
Mehr von Stephen Ritchie
Mehr von Stephen Ritchie (12)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Continuous Integration: Blueprint, Toolbox, Master Craft
- 1. Continuous Integration: Blueprint, Toolbox, Master Craft DC .NET Users Group (@DCDNUG) Stephen D. Ritchie February 2013 Meeting @RuthlessHelp Feb 19, 2013 Stephen D. Ritchie – Managing Consultant – Excella Consulting, Inc., 2300 Wilson Blvd, Suite 630, Arlington, VA 22201 – 703.840.8600 – http://excella.com
- 2. Live Tweet, Slides and Examples • Twitter: @RuthlessHelp • Slides: http://www.slideshare.net/ruthlesshelp • Code Samples: http://github.com/ruthlesshelp Stephen D. Ritchie 2
- 3. The Problem 1 Scott makes changes 2 Susan makes changes 3 You can’t build Source Code 1 3 2 Scott’s Susan’s You Computer Computer Stephen D. Ritchie 3
- 4. What Went Wrong? Conflicts Missing Files Breaking Changes Stephen D. Ritchie 4
- 5. How do you find integration issues? Stephen D. Ritchie 5
- 6. Manual Integration Build Run Some Unit Tests Perform Static Analysis Clean + Rebuild All Stephen D. Ritchie 6
- 7. Continuous Integration Blueprint Stephen D. Ritchie 7
- 8. CI Server Source CI Code Server Scott’s Susan’s You Computer Computer Stephen D. Ritchie 8
- 9. CI Server Triggered by SCM and Stephen D. Ritchie 9
- 10. CI – Per Commit Steps 1. Clean + Rebuild All 2. Run All Unit Tests 3. Analysis Static Code Analysis Coding Standards Stephen D. Ritchie 10
- 11. Continuous Integration Toolbox Stephen D. Ritchie 11
- 12. CI Server – Jenkins http://jenkins-ci.org/ Free Open Source Stephen D. Ritchie 12
- 13. CI Server – Cruise Control http://cruisecontrol.sourceforge.net/ http://www.cruisecontrolnet.org/ Free Open Source Stephen D. Ritchie 13
- 14. CI Server – TeamCity http://www.jetbrains.com/teamcity/ Commercial Easy to Use Stephen D. Ritchie 14
- 15. Perhaps an example would be helpful Stephen D. Ritchie 15
- 16. Continuous Integration Master Craft Stephen D. Ritchie 16
- 17. The Master Craft Unit Testing Plus Code Coverage Stephen D. Ritchie 17
- 18. The Master Craft System Testing Integration Testing Acceptance Testing Stephen D. Ritchie 18
- 19. The Master Craft Code Quality Visualizations Analysis Checks Metrics Detections Stephen D. Ritchie 19
- 20. The Master Craft Reporting And Visibility Stephen D. Ritchie 20
- 21. The Master Craft Packaging And Deployment Stephen D. Ritchie 21
- 22. Stephen’s Contact Info • Email: stephen.ritchie@excella.com • LinkedIn: http://www.linkedin.com/in/sritchie Stephen D. Ritchie 22