Buildbot
- 1. BuildBot Continuous Integration System Willie <willie@issdu.com.tw>
- 2. Agenda How do I use BuildBot?
- 4. Practices of Continuous Integration
- 5. How do I use BuildBot?
- 6. 2. Commit 3. Trigger 4. Wait & See Email If Fail 1. Unit Test
- 7. 1. Update codebase 2. Unit Test 3. Replace the previous one (/home/uagent) 4. Restart 5. Stress Test 6. System Test Help me to find 5+ bugs in the last week.
- 9. BuildBot A continuous integration system
- 10. Help to automate the compile/test cycle
- 12. Screenshot
- 15. Similar projects Hudson (JAVA)
- 16. Similar projects CruiseControl (JAVA)
- 17. Similar projects CruiseControl.NET (C#)
- 18. BuildBot Demo
- 19. Practices of Continuous Integration
- 20. What is CI A software development practice (requires no particular tooling)
- 21. From Extreme Programming development process
- 22. CruiseControl is the first CI system created by ThoughtWorks company.
- 23. Why use CI system Detect integration errors ASAP Fix bugs made in last week: painful
- 24. Fix bugs made in last month: very painful!!!
- 25. People thought... Before It can't work (here).
- 26. Doing it won't make much difference. After Yes we do that – how could you live without it?
- 27. How to use CI system Checkout source code from VCS
- 28. Modify code
- 29. Run self-testing code (ex. unit test)
- 31. Run self-testing code on an
- 33. How to use CI system (cont.) Step 5. can be done automatically by CI system
- 34. Errors is detected rapidly
- 35. A good team should have many correct builds a day
- 36. Bad builds do occur from time to time, but should be quickly fixed
- 37. Practices of CI Maintain a single source repository Put everything required for a build Automate the build Build and launch in a single command
- 38. Need a virgin machine
- 39. Practices of CI (cont.) Make your build self-testing Testing can catch a lot of bugs – enough to be useful Everyone commits every day Conflicts that stay undetected for weeks can be very hard to resolve
- 40. Practices of CI (cont.) Every commit should build the mainline on an integration machine Why: things still go wrong Developers forget to run build before commit
- 41. Environmental differences Manual build & CI system
- 42. Practices of CI (cont.) Keep the build fast The whole point of CI is to provide rapid feedback
- 43. 10 minutes build
- 44. Practices of CI (cont.) Keep the build fast (cont.) Staged build (2 nd build doesn't have the same 'stop everthing' quality)
- 45. Practices of CI (cont.) Keep the build fast (cont.) 2 nd build fails: add another test into commit test suit MySQL story Test in a clone of the production environment Real tests without mocks
- 46. Practices of CI (cont.) Make it easy for anyone to get the latest executable Nightly build Everyone can see what's happening BuildBot demo (countdown) Automate deployment Also needs automated rollback
- 47. Benefits of CI Reduce risk Integration is a long and unpredictable process There's no long integration anymore
- 48. Easier to find bugs and remove them Quality of your test suits
- 49. Where to start 1.Get the build automated An automated nightly build is a fine step 2.Introduce some automated testing into your build Try to identify the major areas
- 50. Where to start (cont.) 3.Try to speed up the commit build Magic 10 mins