c-i

350 views

Published on

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

No notes for slide

c-i

  1. 1. WHY CI?
  2. 2. THE JOEL TEST (AUGUST 2000) 12 STEPS 2. Can you make a build in one step? 3. Do you make daily builds? 5. Do you fix bugs before writing new code?
  3. 3. AGILE1. CI is a less controversial agile practice2. Rapid delivery goal3. Synergistic effect with Unit Testing and Coding Standards
  4. 4. FIXES PROBLEMS broken build lack of integration works for me! find and fix bugs
  5. 5. BENEFITSeasy to know build stateminimize integration effortstatic code analysiseasy to configuregather statisticsearly prediction of fail
  6. 6. WHY ELSEwidespread best practiceestablish confidencereuse existing MSBuild scripts
  7. 7. STATIC CODE ANALYSIS FxCop, StyleCop, CheckStyle NDepend Simian (code duplicates) NDoc, Sandcastle
  8. 8. TOOLSTeam Foundation ServerBamboo QuickBuild, ContinuumCruiseControl/CC.NETJenkins/HudsonTeamCity
  9. 9. CC.NET
  10. 10. CC.NETCannot add/edit a project via web-interface
  11. 11. JENKINS
  12. 12. JENKINS
  13. 13. JENKINSBig setup effort
  14. 14. TEAMCITY
  15. 15. TEAMCITY
  16. 16. TEAMCITYFree up to 20 build configurations
  17. 17. QUESTIONS?

×