Multi-arch CGO binaries via self-hosted runners?

[tashian]

Hi! We're looking to migrate our project step-ca to GoReleaser, and I'm curious about CGO support.

I've seen this done using Docker containers (eg. with hugo, see this issue), and I like that option but it adds a lot of complexity compared to a typical goreleaser config.

But I was kind of curious about an alternative .. I'm wondering if self-hosted GitHub Action runners could be used just for the build step? We could potentially set up build servers for each platform we need to support.

I'm envisioning one goreleaser config for each platform, and those would run in parallel.

But, if we did that, it seems like we'd have to upload the artifacts somewhere at the end, and do the actual release steps with custom code. Which sort of defeats the purpose of using GoReleaser. But, am I missing something here?

[caarlos0]

You could do that, the only thing that might be an issue is the checksums file, since each run will generate a different file (because it will build only for a given target).

If you disable the checksums (or generate them with different names on each platform), it should be fine, I think.

[caarlos0]

This should now be possible with split/merge pipelines in goreleaser pro: https://carlosbecker.com/posts/goreleaser-split-merge/