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
Jorrit,
The simplest solution might be 'go mod vendor' to populate a 'vendor'
directory, and then set '-mod=vendor' or 'GOFLAGS=-mod=vendor' when
building.
If that is not workable for some reason, here is an alternative that is
more similar to your request for a 'go mod download -dir
Can you accomplish what you want with module vendoring? Before I set up my
own Athens proxy, I was using that to avoid DDOSing github in my build
automation, and it seemed to work fine. Your first pipeline step could
vendor in all the modules, and subsequent pipeline steps would use those.
--
