1. Large Scale Continuous Integration

2. Made by: Erik Romson Zenior

3. Presented by: Johannes Brodwall Lead Software Architect BBS

5. (1)

6. Wait a minute…

7. Architect?

8. Reuse and cooperation

9. Release strategy (one code line)

10. Principle: Everyone should be on one build server

11. (2)

12. Consequences

13. Size

15. Build time

17. Error notification is delayed Bad checkin Build starts Build breaks

18. Many developers

19. Whodoneit? 10 suspects Bad checkin Build starts Build breaks

20. (3)

21. How does it look?

22. (disclaimer)

23. 20:04 4,09m

24. 20:15 6,15m

25. 20:24 7,29m

26. 20:35 8,37m

28. 21:28 11,36m

29. 21:53 10,41m

30. 22:12 12,05m

31. (4)

32. How does it work?

34. foo depends on bar-1.1 Maven

35. Continuous build: Quickly after checkin

36. (shouldve caught all mistakes)

37. Integration build: In due time

38. (creates (and deploys some) EARs etc)

39. Daily build: Nightly

40. (generates project-sites)

42. Technology: Maven + Cruisecontrol + massive amounts of custom code

43. Implementation: Cruisecontrol triggers a custom maven plugin which uses beanshell to access a custom Java API that executes Maven goals for modules

44. (I think)

46. (5)

47. Lessons learned

48. What is hard?

49. Somebody has to care about the build time!

50. Culture for following up when the build breaks

51. This one is mine. I forgot to check in a file.

52. But sometimes, things go wrong…

53. Anyone looking into this one? Could xxx please look here ASAP! Hes gone home I will check it out.

54. Notification mails must be easy to interpret

55. Many dependencies

57. Refactoring central modules is expensive

58. (but doable, even in a system with several 100 KLOC)

59. Dont leave the build red while you fix your problems

60. CVS update frequently!

61. Protect yourself with unit tests

62. (6)

63. The road goes ever on

64. Domain Driven Design build server

66. (cruisecontrol = cron on steroids)

67. Smaller units of reporting

68. Concurrent build

69. Build farm

71. Better visibility

73. Thank you for the attention Johannes Brodwall