[build] Use docker to manage dependencies

[jbudz]

The goal of this is to move dependency management under direct control of kibana, instead of relying on the host machine.

This attempts to fix several issues:

• windows specific checks
• the possibility of spawning programs that don't exist - wc, shasum, zip, etc.
• version management
• global conflicts on the host machine

With docker and docker-compose installed, building should work the same as it did previously.

npm run build
npm run build -- --skip-os-packages
npm run build -- --skip-archives

[jbudz]

Before: node_modules/.bin/grunt build 6:35.95 total
After: npm run build 14:41.78 total

[jbudz]

I'm going to revert the change that runs this on CI so we can unblock this. For now it can be considered ease of use utility.

[tylersmalley]

I would like to get this running on CI to avoid having multiple paths this could go through. I also think that getting Docker in CI will allow us to utilize it more in the future.

[jbudz]

jenkins, test it

[tylersmalley]

We should note Docker being a dependency for creating builds.

[jbudz]

jenkins, test it

[jbudz]

This should be good to go now. Finally.

[tylersmalley]

I believe there are alpine images available for this, just append -alpine.

[jbudz]

can't yet. the node image is based on 3.4 and rpm isn't available https://pkgs.alpinelinux.org/packages?name=rpm&branch=&repo=&arch=&maintainer=

[tylersmalley]

I have been playing around with this off-and-on, and I am not sure about doubling the build times.

Thoughts on having a task to build and publish the container to our docker repository? I am curious how much time that will shave off or how close it would get to the current build time.

[jbudz]

We could, but we'd have to remove

 +RUN bundle install --deployment
 +RUN npm install

so we don't end up with wrong versions. I'll do some timing on this and see if there's other options too.

[jbudz]

Closing until I revisit, I haven't been working on this.