during the build process. This install can be time consuming and docker should be able to reuse the bundle maven produces.
When maven is run, the target directory contains the following:
@ C:\work\digital_services_bpa\coding-challenge-app\target
$ ls
Jars_jruby9-exec.lock dsbpa-1.00-SNAPSHOT.war rubygems
The entirety of the rubygems folder should be copied to the docker container that currently runs the bundle install. In that docker container the GEM_HOME environment variable should be set as follows:
export GEM_HOME=/path/to/rubygems
such that an ls would look like:
$ cd %GEM_HOME%
@ C:\work\digital_services_bpa\gem_home
$ ls
bin build_info cache doc extensions gems specifications
To test the setup, running a bundle install in the docker container should yield something like:
$ bundle install
Using rake 12.3.3
Using concurrent-ruby 1.1.5
Using i18n 1.6.0
Using minitest 5.11.3
Using thread_safe 0.3.6 (java)
Using tzinfo 1.2.5
Using activesupport 5.2.3
Using builder 3.2.3 **etc**
At this point the bundle install should be removable.
Currently both maven and docker execute a:
during the build process. This install can be time consuming and docker should be able to reuse the bundle maven produces.
When maven is run, the target directory contains the following:
The entirety of the rubygems folder should be copied to the docker container that currently runs the bundle install. In that docker container the GEM_HOME environment variable should be set as follows:
such that an ls would look like:
To test the setup, running a bundle install in the docker container should yield something like:
At this point the bundle install should be removable.