Trip down the memory lane of different CI/build pipeline organisation

1. The path to repeatable
builds

2. Andrzej Grzesik
@ags313
andrzej@grzesik.it
andrzejgrzesik.info

3. about:me

5. disclaimers

6. my opinions are my own

7. any resemblance (…)
purely coincidental ;-)

8. I hate computers

9. questions?
shoot!

10. episode I
the New

11. ad-hoc, manual Jenkins
new department
needed something to run the code

12. how this ended:
‘dev’ desktop turned CI
‘magic’, ‘mysticism’, problems and pain
1/11, would not do again

13. episode II
node wars

15. machines failed
surprise

16. more builds, more wait

17. fix

18. how this ended:
better: experimentation and no-fear
5/11, not a bad start

19. episode III
revenge of the VMs

20. because

21. reality
certain software doesn’t like automation
did: VM, treasure the image, run away

22. more builds, more wait?
cheffing Jenkins && nodes (good)
cheffing Jenkins configuration (not so)
backups for Jenkins
ganglia to look at nodes
8/11, stable

23. episode IV
mobile menace

24. mobile menace
automating mobile testing
grid for iOS Selenium Driver
everybody uses mac minis ;-)

25. mobile menace
64 OSX VMs ++ chef server
logstash to collect and analyze chef logs
VMWare to power VMs because Vsphere

26. mobile menace
OSX is full of quirks!
needed quick node rebuild a bit too often
10 - 1/11, it still works!

27. episode V
bad idea of the century

28. X in a box.

29. X in a box.
as in, *whole* prod in a box

30. starts innocent

31. results
all dependencies in one place
easy to integration test
easy to deploy MY stuff

38. grows into…

39. results
“so much space still to consume”
dependency spaghetti
NEG_INFINITY/11

40. episode VI
Return(?) of the

41. breaks a bit, so good for hacking

42. caveat: java, maven && stuff
solution: images with SBT

44. not so fast
Devs “love” OSX!
Dependencies
boot2docker runs out of…

45. episode VII
don’t know ;-)