Continuous Integration, Fast Builds And Flot, By Chris Bushell, February 3rd 2010

1. Continuous Integration, Fast Builds and Flot Chris Bushell - Melbourne Patterns Group February 3rd 2010

2. Traditional Software Development Waterfall Development happens independently, in parallel streams Integration phase

3. Integration Is Painful Time consuming Unpredictable

4. Typical Software Development

5. Continuous Integration Single source code repository Automated build Automated tests Frequent commits

6. CI In Practice – Check Out Time

7. CI In Practice – Write Code Time

8. CI In Practice – Run Build Time

9. CI In Practice – Commit Time

10. CI In Practice Time

11. CI In Practice – Continuous Build Time

12. Encourage Frequent Check-Ins Integrating small changes is much less painful and time consuming than integrating large changes

13. Problem - Builds Can Become Slow More code = more tests = longer build time

14. A Fast Build Is Essential Idle developers Context switching Unable to deliver new features I get bored easily

15. Monitoring Build Time Need to measure how long your build takes

16. Continuous Integration Server API allows us to access historic build time information

17. Flot Demo

18. Speeding Up A Slow Build Split code base

19. Speeding Up A Slow Build Hardware SSD

20. Speeding Up A Slow Build Think about how to test Unit tests are fast Functional testing can be slow

21. Speeding Up A Slow Build Isolation from slow dependencies Impersonator pattern

22. Speeding Up A Slow Build Parallelize build Be careful with shared dependencies

23. Speeding Up A Slow Build Choose a light weight development container

24. Speeding Up A Slow Build Sam Newman’s Build Patterns Check In Gate Fish Eye Test Suite Build Time Limit