Ignite: Open Source Continuous Integration

1,921 views

Published on

Open Source Continuous Integration
Patrick Reynolds,
Kitware Inc.

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Ignite @ Mil-OSS WG2: Open Source Continuous Integration from Joshua L. Davis on Vimeo.<br /><object type="application/x-shockwave-flash" data="http://vimeo.com/moogaloop.swf?clip_id=13979499&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0" width="350" height="288"><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=13979499&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0"></param><embed src="http://vimeo.com/moogaloop.swf?clip_id=13979499&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0" width="350" height="288" type="application/x-shockwave-flash"></embed></object>
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
1,921
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
17
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Ignite: Open Source Continuous Integration

  1. 1. Open Source Continuous Integration Patrick Reynolds Kitware, Inc.
  2. 2. Inertia • Open Source Software needs to be far better than the alternatives
  3. 3. The Value of Software
  4. 4. “Free” Shocks People
  5. 5. Credibility • Determined by reputation and price • OSS needs something better
  6. 6. Open the Code
  7. 7. Open the Testing Process
  8. 8. Open Everything
  9. 9. The More Metrics the Better • Coding Style • Coverage • Dynamic Analysis • Static Analysis • Packaging
  10. 10. Lots of Tools • CMake, CTest, CDash, etc. • Ant, JUnit, Hudson, etc. • The list goes on
  11. 11. CMake, CTest, CDash, etc. • Integrated stack of tools • Accomplish our listed goals for continuous integration
  12. 12. CDash
  13. 13. Keep Developers Honest • Easy to see who “broke the build” • Nightly and Continuous Builds • Style Builds
  14. 14. Engage Users • Experimental Builds • Users see the whole process instead of just the code. • Proof of cross-platform support
  15. 15. From Theory to Practice • Bad Workflow • Better Workflow • Best Workflow
  16. 16. Bad Workflow • Commit Code • Cross fingers • Get angry emails from users
  17. 17. Better Workflow • Write Tests • Write Code • Test Code • Commit Code • Get angry emails from OSX and Windows users
  18. 18. Best Workflow • Write Tests • Write Code • Test Code • Commit Code • Fix the OSX and Windows bugs emailed to you from the dashboards
  19. 19. Results • Quality metrics that outclass those of proprietary Software • Less worry, more fun.
  20. 20. Thank You Patrick Reynolds Kitware Inc. http://www.kitware.com patrick.reynolds@kitware.com

×