🍊 ARM your continuous integration system with fruits! 🍌

Being able to build/test/deploy on a remote machine each time we commit has been a major progress for us, developers. 🚀

Furthermore, by using Docker, things have been so much easier! No more dependency hell when you have to build and test two incompatible products.

This solution looks almost perfect… until you reach a threshold.

As your Gitlab-ci will become more and more popular within your organization, you may experience longer waiting queues until the next batch of Runners is released.

So you may go from praising the CI to cursing the CI.

You maybe have a Raspberry Pi taking dust on your desk or in your drawer. What’s the point? What’s the connection with the CI?

Well… What if I told you you could transform this momentarily useless piece of hardware into a brand new Gitlab-ci Runner? This way, you could shorten the time your jobs spend in the queue.

But wait, there is more. What if there was a cheaper solution that could allow you to create a Gitlab-ci Runner for a 15€ investment? You may have heard about Banana Pi, Orange Pi, and other variations of fruit Pi(e). The competition is harsh between these manufacturers, and you can find pretty nifty machines for darn cheap. These machine can run Docker, and even Gitlab-Runner on top of it.

What if you could even build Docker images through CI on these machines?

Is this even possible?

It is. You shall leave this talk by knowing the basics to start your own Gitlab Runner for 15€.

Transcript

1. Bruno Verachten ARM your continuous integration system with fruits! bruno.verachten worldline.com poddingue
2. Bruno Verachten ARM your ci system with fruits!
3. Bruno Verachten ARM your ci system with fruits! SBC STANDS FoR Single Board Computer
4. Bruno Verachten ARM your continuous integration system with fruits! Judge me by my size, do you?
5. Bruno Verachten ARM your continuous integration system with fruits! Judge me by my size, do you?
6. Bruno Verachten What iS Gitlab-Ci?
7. Bruno Verachten Continuous integration with Gitlab • Multi platform
8. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language
9. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable
10. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable • Parallel builds
11. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable • Parallel builds • Realtime logging
12. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable • Parallel builds • Realtime logging • Versioned tests
13. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable • Parallel builds • Realtime logging • Versioned tests • Pipeline
14. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable • Parallel builds • Realtime logging • Versioned tests • Pipeline • Build artifacts
15. Bruno Verachten Continuous integration with Gitlab • Multi platform • Multi language • Stable • Parallel builds • Realtime logging • Versioned tests • Pipeline • Build artifacts • Docker support
16. Bruno Verachten Continuous integration with Gitlab
17. Bruno Verachten Continuous integration with Gitlab
18. Bruno Verachten Continuous integration with Gitlab
19. Bruno Verachten Continuous integration with Gitlab
20. Bruno Verachten • Continuous integration with Gitlab
21. Bruno Verachten • Continuous integration with Gitlab
22. Bruno Verachten • Continuous integration with Gitlab
23. Bruno Verachten • Continuous integration with Gitlab
24. Bruno Verachten • Continuous integration with Gitlab
25. Bruno Verachten • Ci with Gitlab / RUNNERS
26. Bruno Verachten • Ci with Gitlab / RUNNERS
27. Bruno Verachten • Ci with Gitlab / RUNNERS
28. Bruno Verachten • Ci with Gitlab / RUNNERS
29. Bruno Verachten • Ci with Gitlab / RUNNERS
30. Bruno Verachten • Ci with Gitlab / RUNNERS
31. Bruno Verachten • Continuous integration with Gitlab
32. Bruno Verachten • Continuous integration with Gitlab
33. Bruno Verachten • Continuous integration with Gitlab
34. Bruno Verachten • Continuous integration with Gitlab
35. Bruno Verachten What is A Runner/SHARED
36. Bruno Verachten • Why would you need your own Runner?
37. Bruno Verachten •
38. Bruno Verachten • Why would you need your own Runner?
39. Bruno Verachten • Why would you need your own Runner?
40. Bruno Verachten • Why would you need your own ARM Runner?
41. Bruno Verachten • Why would you need your own ARM Runner?
42. Bruno Verachten • Why would you need your own ARM Runner?
43. Bruno Verachten • Why would you need your own ARM Runner? SBC STANDS FoR Single Board Computer
44. Bruno Verachten • Why would you need your own ARM Runner?
45. Bruno Verachten • Why would you need your own ARM Runner?
46. Bruno Verachten • Why would you need your own ARM Runner?
47. Bruno Verachten • Why would you need your own ARM Runner?
48. Bruno Verachten • Why would you need your own ARM Runner?
49. Bruno Verachten Let’s install a Runner
50. Bruno Verachten Direct installation
51. Bruno Verachten Direct installation
52. Bruno Verachten Direct installation
53. Bruno Verachten Direct installation
54. Bruno Verachten Registration
55. Bruno Verachten Registration
56. Bruno Verachten Registration
57. Bruno Verachten Registration
58. Bruno Verachten Registration
59. Bruno Verachten Registration
60. Bruno Verachten Registration
61. Bruno Verachten Registration
62. Bruno Verachten Registration/Executor
63. Bruno Verachten Registration/Executor
64. Bruno Verachten Registration/Executor
65. Bruno Verachten Registration/Executor
66. Bruno Verachten Let’s install aN ARM Runner
67. Bruno Verachten • Docker image Klud • And that’s all folks, can you believe it? Why a Raspberry Pi?
68. Bruno Verachten • Docker image Klud • And that’s all folks, can you believe it? Why a Raspberry Pi?
69. Bruno Verachten 39 • What if… Docker on Pi? Really?
70. Bruno Verachten 39 • What if… Docker on Pi? Really?
71. Bruno Verachten 39 • What if… Docker on Pi? Really?
72. Bruno Verachten Downloading and installing the Hypriot Distro 40
73. Bruno Verachten Downloading and installing the Hypriot Distro 40
74. Bruno Verachten Writing the Hypriot image 42
75. Bruno Verachten Writing the Hypriot image 42
76. Bruno Verachten Writing the Hypriot image 42 REAL
77. Bruno Verachten Writing the Hypriot image 42 REAL GENUiNE
78. Bruno Verachten 44 Booting THE Pi for the first time
79. Bruno Verachten 44 Booting THE Pi for the first time
80. Bruno Verachten 44 Booting THE Pi for the first time
81. Bruno Verachten 44 Booting THE Pi for the first time
82. Bruno Verachten 44 Booting THE Pi for the first time
83. Bruno Verachten 46 Machine name and user password
84. Bruno Verachten 46 Machine name and user password
85. Bruno Verachten 46 Machine name and user password
86. Bruno Verachten 46 Machine name and user password
87. Bruno Verachten 49 Docker / Date
88. Bruno Verachten 49 Docker / Date
89. Bruno Verachten 49 Docker / Date
90. Bruno Verachten 51 Almost there
91. Bruno Verachten 51 Almost there
92. Bruno Verachten 51 Almost there
93. Bruno Verachten 51 Almost there
94. Bruno Verachten Almost there
95. Bruno Verachten 53 Gitlab runner registration
96. Bruno Verachten 53 Gitlab runner registration
97. Bruno Verachten 53 Gitlab runner registration
98. Bruno Verachten 53 Gitlab runner registration
99. Bruno Verachten 53 Gitlab runner registration
100. Bruno Verachten 53 Gitlab runner registration
101. Bruno Verachten 53 Gitlab runner registration
102. Bruno Verachten 53 Gitlab runner registration
103. Bruno Verachten 54 Gitlab runner / building Docker images
104. Bruno Verachten 54 Gitlab runner / building Docker images
105. Bruno Verachten 54 Gitlab runner / building Docker images
106. Bruno Verachten 54 Gitlab runner / building Docker images
107. Bruno Verachten 55 Gitlab runner / building Docker images
108. Bruno Verachten 55 Gitlab runner / building Docker images
109. Bruno Verachten 55 Gitlab runner / building Docker images
110. Bruno Verachten 55 Gitlab runner / building Docker images
111. Bruno Verachten 55 Gitlab runner / building Docker images
112. Bruno Verachten Let’s install a cheap arm runner 56
113. Bruno Verachten Let’s install a cheap arm runner 56
114. Bruno Verachten 57 Gitlab runner for 9
115. Bruno Verachten 57 Gitlab runner for 9
116. Bruno Verachten 57 Gitlab runner for 9
117. Bruno Verachten 57 Gitlab runner for 9
118. Bruno Verachten 58 Gitlab runner for 9 on armbian
119. Bruno Verachten 58 Gitlab runner for 9 on armbian
120. Bruno Verachten 58 Gitlab runner for 9 on armbian
121. Bruno Verachten 58 Gitlab runner for 9 on armbian
122. Bruno Verachten 60 Gitlab runner for 9 on armbian
123. Bruno Verachten 60 Gitlab runner for 9 on armbian
124. Bruno Verachten 60 Gitlab runner for 9 on armbian
125. Bruno Verachten 61 Gitlab runner for 9 on armbian
126. Bruno Verachten 61 Gitlab runner for 15 on armbian
127. Bruno Verachten 61 Gitlab runner for 15 on armbian
128. Bruno Verachten 61 Gitlab runner for 15 on armbian
129. Bruno Verachten 61 Gitlab runner for 15 on armbian
130. Bruno Verachten ARM64: Status 66
131. Bruno Verachten ARM64 STATUS
132. Bruno Verachten ARM64 STATUS
133. Bruno Verachten ARM64 STATUS
134. Bruno Verachten 68 Takeaways
135. Bruno Verachten 68 Takeaways
136. Bruno Verachten 68 Takeaways
137. Bruno Verachten 68 Takeaways
138. Bruno Verachten 68 Takeaways
139. Bruno Verachten 68
140. Bruno Verachten 68 Takeaways
141. Bruno Verachten 68 Takeaways
142. Bruno Verachten 68 Takeaways
143. Bruno Verachten 68 Takeaways
144. Bruno Verachten Thanks For more information please contact: Poddingue bruno.verachten Worldline.com