Continuous Integration: Blueprint, Toolbox, Master Craft

4,195 views

Published on

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.

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
4,195
On SlideShare
0
From Embeds
0
Number of Embeds
3,022
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Continuous Integration: Blueprint, Toolbox, Master Craft

  1. 1. Continuous Integration: Blueprint, Toolbox, Master Craft DC .NET Users Group (@DCDNUG) Stephen D. Ritchie February 2013 Meeting @RuthlessHelp Feb 19, 2013Stephen D. Ritchie – Managing Consultant – Excella Consulting, Inc., 2300 Wilson Blvd, Suite 630, Arlington, VA 22201 – 703.840.8600 – http://excella.com
  2. 2. Live Tweet, Slides and Examples• Twitter: @RuthlessHelp• Slides: http://www.slideshare.net/ruthlesshelp• Code Samples: http://github.com/ruthlesshelpStephen D. Ritchie 2
  3. 3. The Problem1 Scott makes changes2 Susan makes changes3 You can’t build Source Code 1 3 2 Scott’s Susan’s You Computer ComputerStephen D. Ritchie 3
  4. 4. What Went Wrong? Conflicts Missing Files Breaking ChangesStephen D. Ritchie 4
  5. 5. How do you find integration issues?Stephen D. Ritchie 5
  6. 6. Manual Integration Build Run Some Unit Tests Perform Static Analysis Clean + Rebuild AllStephen D. Ritchie 6
  7. 7. Continuous Integration BlueprintStephen D. Ritchie 7
  8. 8. CI Server Source CI Code Server Scott’s Susan’s You Computer ComputerStephen D. Ritchie 8
  9. 9. CI ServerTriggered by SCM andStephen D. Ritchie 9
  10. 10. CI – Per Commit Steps 1. Clean + Rebuild All 2. Run All Unit Tests 3. Analysis Static Code Analysis Coding StandardsStephen D. Ritchie 10
  11. 11. Continuous Integration ToolboxStephen D. Ritchie 11
  12. 12. CI Server – Jenkins http://jenkins-ci.org/ Free Open SourceStephen D. Ritchie 12
  13. 13. CI Server – Cruise Control http://cruisecontrol.sourceforge.net/ http://www.cruisecontrolnet.org/ Free Open SourceStephen D. Ritchie 13
  14. 14. CI Server – TeamCity http://www.jetbrains.com/teamcity/ Commercial Easy to UseStephen D. Ritchie 14
  15. 15. Perhaps an example would be helpfulStephen D. Ritchie 15
  16. 16. Continuous Integration Master CraftStephen D. Ritchie 16
  17. 17. The Master Craft Unit Testing Plus Code CoverageStephen D. Ritchie 17
  18. 18. The Master Craft System Testing Integration Testing Acceptance TestingStephen D. Ritchie 18
  19. 19. The Master Craft Code QualityVisualizations AnalysisChecksMetricsDetectionsStephen D. Ritchie 19
  20. 20. The Master Craft Reporting And VisibilityStephen D. Ritchie 20
  21. 21. The Master Craft Packaging And DeploymentStephen D. Ritchie 21
  22. 22. Stephen’s Contact Info• Email: stephen.ritchie@excella.com• LinkedIn: http://www.linkedin.com/in/sritchieStephen D. Ritchie 22

×