We use a docker-based workflow to get consistent runs. Note that we use
stretch images for newer ruby versions and do some ssl hackery - more
recent debian versions see SSL test failures related to unsupported
ciphers, etc. Rather than debug them now, we ignore them - they're not
likely related directly to the code we're testing.
We also hack up the ruby docker image; because they do this strange
thing where they install gems globally into one bundle. It messes up
this build process, so we undo it to the best of our ability.