Open Source Continuous Integration Patrick Reynolds, Kitware Inc.

1. Open Source
Continuous Integration
Patrick Reynolds
Kitware, Inc.

2. Inertia
• Open Source Software needs to be far better
than the alternatives

3. The Value of Software

4. “Free” Shocks People

5. Credibility
• Determined by reputation
and price
• OSS needs something
better

6. Open the Code

7. Open the Testing Process

8. Open Everything

9. The More Metrics the Better
• Coding Style
• Coverage
• Dynamic Analysis
• Static Analysis
• Packaging

10. Lots of Tools
• CMake, CTest, CDash, etc.
• Ant, JUnit, Hudson, etc.
• The list goes on

11. CMake, CTest, CDash, etc.
• Integrated stack of tools
• Accomplish our listed goals for continuous
integration

12. CDash

13. Keep Developers Honest
• Easy to see who “broke the build”
• Nightly and Continuous Builds
• Style Builds

14. Engage Users
• Experimental Builds
• Users see the whole process instead of just the
code.
• Proof of cross-platform support

15. From Theory to Practice
• Bad Workflow
• Better Workflow
• Best Workflow

16. Bad Workflow
• Commit Code
• Cross fingers
• Get angry emails from users

17. Better Workflow
• Write Tests
• Write Code
• Test Code
• Commit Code
• Get angry emails from OSX and Windows users

18. Best Workflow
• Write Tests
• Write Code
• Test Code
• Commit Code
• Fix the OSX and Windows bugs emailed to you
from the dashboards

19. Results
• Quality metrics that outclass those of proprietary
Software
• Less worry, more fun.

20. Thank You
Patrick Reynolds
Kitware Inc.
http://www.kitware.com
patrick.reynolds@kitware.com