Hypothetically, it would be pretty great if every test suite than ran on a Jenkins server had a self contained environment to put it's dependencies in rather than installing dependencies for every application on the Jenkins host. Less hypothetically, this PR adds some facilities to do such a thing.
Assuming you have docker installed, tests can now be run with a simple bin/test_docker_build.sh
Notable Changes
Some changes were made to WorkDir, specifically so that GEM_PATH can be injected into it's environment. In testing, we were seeing that the bundler gem wasn't available in gem list, which makes sense, because when tests are executed within bundle exec, only Gems in that bundle are available, and Bundler generally isn't actually listed in bundles.
Meme
me trying to figure out gem paths inside a ruby process inside bundler inside docker
Purpose
Hypothetically, it would be pretty great if every test suite than ran on a Jenkins server had a self contained environment to put it's dependencies in rather than installing dependencies for every application on the Jenkins host. Less hypothetically, this PR adds some facilities to do such a thing.
Assuming you have docker installed, tests can now be run with a simple
bin/test_docker_build.sh
Notable Changes
Some changes were made to
WorkDir
, specifically so thatGEM_PATH
can be injected into it's environment. In testing, we were seeing that thebundler
gem wasn't available ingem list
, which makes sense, because when tests are executed withinbundle exec
, only Gems in that bundle are available, and Bundler generally isn't actually listed in bundles.Meme
me trying to figure out gem paths inside a ruby process inside bundler inside docker