I'll test the GOPROXY approach, although vendoring leads to faster builds
(but requires more actions before committing changes).
Thanks, Jorrit
On Monday, March 4, 2019 at 10:17:29 PM UTC+1, thepud...@gmail.com wrote:
>
> Jorrit,
>
> The simplest solution might be 'go mod vendor' to populate a '
I indeed managed to use 'go mod vendor', which leads to much faster builds
anyway. But it would be nice if the module tooling compared the vendor
directory to match the checksums in go.sum, otherwise you can update on of
your dependencies but forget about updating the vendored copy. Do you know
I'd like to be able to use go mod download to download packages to another
directory than GOPATH/pkg/mod and automatically have all go commands be
aware of this new location.
This is specifically for CI/CD to ensure I can download modules in one
stage and use them in subsequent stages.
I'm
