I'm aware of multistage builds, but I don't think it will add a lot of value in this case. I also had some issues with it on the Dockerhub builder when using multistage. Then the imported file from the earlier stage would be 0bytes.
The reason I don't think it is useful, for the CI we won't cache the image at all. The `build.sh docker-test` will run on the CI, and for now it doesn't store the image somewhere. For local development, it makes more sense to use `build.sh docker`. Also, if the Dockerfile isn't changed, the layers are cached and it will just reuse the existing image. [ Full content available at: https://github.com/apache/avro/pull/336 ] This message was relayed via gitbox.apache.org for [email protected]
