A presentation given at DevOps DownUnder May 2010. Code at http://github.com/alecthegeek/gitbuilding Updated Nov 2010 for OSDC Melbourne

1. Build Audit and Processes A line of sight from DEV to PROD

2. Alec Clews http://alecthegeek.wordpress.com/ http://twitter.com/alecthegeek http://github.com/alecthegeek Voga Consulting http://voga.com.au/ Licensed under Creative Commons Attribution-Share Alike 2.5 Australia License

4. Using Open Source Tools (Make and Git) as a framework for a controlled build process

6. Auditing and logging requirements for system build

8. The Driver script

9. The output

11. Desire to provide a business value quickly

12. Communicate effectively between team members

15. Implement the change (hack the code and desktop build/testing)

16. Integration build and unit test

17. System Build in a controlled environment

18. System Testing (or UAT, or beta, or ...)

19. Release for distribution or production

21. Runs unit tests

22. Sets up for unit testing framework

23. Happens automagically

24. May only build small pieces

25. May include code instrumentation and additional debugging options

27. Needs documentation

28. May have large scope

30. Ask the developer for already built software!

37. Must be done in a controlled environment

38. Must be done with pre-defined scripts and documented process

39. Scripts should be under version control

40. A record should be keep of all system builds

44. The host image can be archived as changes are made

46. Tools and their settings

49. We can extract our built files at any time – now we can “re-create the build” just by fetching files from version control

50. If our change ticket system is integrated into version control we can identify which changes when into a build

52. Our KPI may depend on SLAs and process outcomes

54. Solid documentation

55. Reduced rework

58. Make

61. Baselines are created using tags. A tag is a label attached to a commit

63. A Build Configuration. Documentation of the environment in which the build is being done (e.g. Platform, compiler, library versions...)

65. A side affect is that your makefile is more efficient!

68. We must re-calculate the dependencies at make time if the source files or header files change

72. o/a.o d/a.d: src/a.c h/a.h

73. Include the dependency file in the makfile

74. # Find the name of all the Dynamic dependency file and include them

75. include $(patsubst $(OBJ_DIR)/%, $(DEP_DIR)/%, $(patsubst %.o,%.d, $(OBJ)))

79. Example BFL BLD_FLAGS [cc -ansi] a275bd53898b96ff56682992cfef600c8d9172b6 BLD_ENV 8b137891791fe96927ad78e64b0aad7bded08bdc src/a.c fbb2a1faee180bd3c81d6d00bb39d1bb68b51725 h/a.h 8ed2304c36b99ef1fd9a1f22a41ee2afe4eb995e makefile 34e0b0adb203123c8ebfdf2c4fb059ff0c942e27 d/main.d 3045b0da533f900bf1ab044de22725475d4d171c d/a.d 8bbf937c5cc911242a3b3fdc531c5d1a5cf7f37c d/b.d bba81a7805d40e267b139a01f69c15c676d0a82d

81. Add the new target to the repository git add b/$(@F).bfl git add $(@)

83. The Build Configuration. A simple string representing the build environment

84. host name of build machine – usually not important unless problem

85. DEMO

90. Check build configuration for target on build tag against current environment – must match

91. Check command line switches – must match

92. We don't care about dates and time

96. problems because text files change? (tool dependent)

97. ....

99. “ Continuous Integration” by Martin Fowler http://www.martinfowler.com/articles/continuousIntegration.html