the path to repeatable builds
TRANSCRIPT
The path to repeatable builds
about:me
disclaimers
my opinions are my own
any resemblance (…)purely coincidental ;-)
I hate computers
questions?shoot!
episode Ithe New
ad-hoc, manual Jenkins
new department
needed something to run the code
how this ended:
‘dev’ desktop turned CI
‘magic’, ‘mysticism’, problems and pain
1/11, would not do again
episode IInode wars
machines failedsurprise
more builds, more wait
fix
how this ended:
better: experimentation and no-fear
5/11, not a bad start
episode IIIrevenge of the VMs
because
reality
certain software doesn’t like automation
did: VM, treasure the image, run away
more builds, more wait?
cheffing Jenkins && nodes (good)
cheffing Jenkins configuration (not so)
backups for Jenkins
ganglia to look at nodes
8/11, stable
episode IVmobile menace
mobile menace
automating mobile testing
grid for iOS Selenium Driver
everybody uses mac minis ;-)
mobile menace
64 OSX VMs ++ chef server
logstash to collect and analyze chef logs
VMWare to power VMs because Vsphere
mobile menace
OSX is full of quirks!
needed quick node rebuild a bit too often
10 - 1/11, it still works!
episode Vbad idea of the century
X in a box.
X in a box.as in, *whole* prod in a box
starts innocent
results
all dependencies in one place
easy to integration test
easy to deploy MY stuff
grows into…
results
“so much space still to consume”
dependency spaghetti
NEG_INFINITY/11
episode VIReturn(?) of the
breaks a bit, so good for hacking
caveat: java, maven && stuff
solution: images with SBT
not so fast
Devs “love” OSX!
Dependencies
boot2docker runs out of…
episode VIIdon’t know ;-)