The document discusses the importance of builds and continuous integration (CI) in the development process, highlighting the need for effective tools and patterns. It covers various types of build scripts, CI tools, and configurations while emphasizing the benefits of automated processes. Additionally, it suggests a gradual approach to building and deploying software by starting with basic features and incrementally enhancing them.

1. Beautiful @RoyOsherove
Builds Bouvet

2. roy@osherove.com
courses
consulting
beautifulbuilds.com

3. Why do we have builds?

4. Builds and tests are made to be broken

5. What’s beautiful?
• See flow
• Ease of change
• Coherent

6. Recommendations
• Use the right tools for build and CI
• Use the right patterns to allow extra benefits

7. Part of a Build Process
• Build Script/editor
• Build Server / CI Server
• Build Environments

8. What’s the difference?
• Automated Build (what to do)
• Continuous Integration (when to do it)

9. Build Scripts (Bat)
Procedural

10. Xml Build Scripts (Ant) - declarative

11. Domain Specific
Language Build
Scripts (Rake)
declarative

12. Declarative
• [Ant, nant,msbuild] (http://ant.apache.org/)
• [Automake] (http://www.gnu.org/software/automake/)
• [Boost Build] (http://www.boost.org/doc/tools/build/index.html)
• [Cmake] (http://www.cmake.org/)
• [Make] (http://www.gnu.org/software/make/)
• [Ocamlbuild] (http://gallium.inria.fr/~pouillar/)
• [Omake] (http://omake.metaprl.org/index.html)
• [Qmake] (http://doc.trolltech.com/4.2/qmake-manual.html)
• [Rake] (http://rake.rubyforge.org/)
• [SCons] (http://www.scons.org/)
• [Waf] (http://code.google.com/p/waf/)

13. Procedural
• FinalBuilder
• Visual build pro
• Batch files
• Powersell scripts

14. Visual Build Scripts (FinalBuilder)

15. Which one?
• Visual editing allows seeing FLOW
• Easy to update and change by newbies
• Easy to debug
• FinalBuilder or Visual Build Pro on windows
• Rake on linux or mac

16. The Right CI Tools

17. TeamCity

18. Jenkins

19. CruiseControl

20. Hudson

21. Many others. Which one?
• Support build agents
• Support amazon ec2 auto scaling agents
• Easy to setup and maintain
• Free for a small team
• TeamCity is awesome

22. But some CI servers support build
actions too!

23. Hardware
• Build Machine (with teamcity)
– + agent machines (optional)
• Test Machine
• Staging Machine
• Production Machine
• This can all be in the cloud (EC2 is wonderful)

24. Build Configurations
• Continuous Integration Build
• Slow Build (nightly, optional)
• Deploy to test servers
• Deploy to staging servers (optional)
• Deploy to production

26. Build Script Injection
• Allow version aware builds
• Build scripts are part of source control
• Build configurations on the CI server are dumb
triggers

27. Fill In The Blanks
• Build Script uses placeholders for system
related knowledge
• Placeholders are filled from environment
variables or other types of parameters to the
command line
• These variables are SET by the Build
Configuration on the CI server

29. Location Agnostic Scripts

30. Extract Script

31. Build Chain Triggers
Triggered by checkin
Triggered by end of previous
Manual
Manual

32. Slow Builds
Do X
Do X + Y
Do X + Y + Z
Do X + y + Z + N

33. Cumulative, Fast Builds

34. How Fast?

35. Shipping Skeleton
• Start by releasing
• Deploy a hello world empty skeleton
• Then fill out the product
• Continue adding small build features as you go
along

36. roy@osherove.com
courses
consulting
beautifulbuilds.com

37. @RoyOsherove
Bouvet