mmiklavc commented on issue #1501: Metron-2246 rpm-docker - minimise use of bind mounts due to performance URL: https://github.com/apache/metron/pull/1501#issuecomment-528110304 > This PR restructures the rpm-docker project to use a three-stage docker build process. The first docker file is a template with the RPM building tools installed, that will be cached by docker once it is build. That's excellent > The second phase of the docker build process involves constructing a new docker image based on the 1st phase docker image plus the Metron jars. This makes me nervous. Can you clarify this a bit more? How is this going to impact the build lifecycle for fulldev? If I do a `vagrant up` can I expect this step is still going to completely rebuild and package Metron with the latest code and deploy fresh, not an old cached version of the jars?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
