Issues with recent builds

[mjpitz]

Opening for transparency. I've noticed some sporadic issues with our builds due to the fetch for go-groups.

Upstream issue: indeedeng/go-groups#20

Some thoughts on how we can add stability:

• Build intermediary containers for our CI pipelines where possible
  • Should be easy to do with existing dockerfiles infrastructure
  • This will reduce our dependency on fetching from Indeed all the time

[abitrolly]

Is that still an issue?

[mjpitz]

Yes. I still encounter issues with it from time to time. I'm half tempted to clone the repo and build it myself because of how often builds fail resolve stuff from oss.indeed.com

[abitrolly]

https://oss.indeed.com/ is 404 for me. Should there be something different?

[mjpitz]

You have to hit a specific path on it. For example, /go is a go module proxy.

[abitrolly]

So you mean https://oss.indeed.com/ is not a depscloud installation, but some kind of go package server. Why it is not possible to go build directly from https://github.com/indeedeng/go-groups ?

[mjpitz]

Yes. And I can build directly from the repo, just requires a bit more work to do.