livepeer / livepeer/go-livepeer

Cross-compile Go amd64 binaries for macOS, Windows and Linux from a single CI environment

Open
#2,156 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: devex type: feature type: tech debt
Dominant language
Go
Stars
586
Forks
226
Avg merge
1d 17h
Merged PRs (30d)
19

Description

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

At the moment, we have a CI environment for each platform we support. This has a number of negative effects including:

  • Requires us to maintain CI pipelines for each of these platforms which is already a chore, but also becomes even more painful whenever the CI pipeline for a specific platform breaks due to packaging issues (looking at you Windows)
  • It is currently difficult to pin a specific Go version for the Windows CI pipeline since it relies on MSYS which does not support installation of older package versions

Describe the solution you'd like
A clear and concise description of what you want to happen.

Since Go supports cross-compiling I wonder if it could be worthwhile to cross-compile Go binaries from a single environment. However, if this still requires compiling ffmpeg in different environments then this might not be as useful...but it at the very least would allow us to pin Go versions and use a single environment for compiling Go code?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by mapping the existing CI environment for each supported platform and reviewing how Go compilation, MSYS, and ffmpeg packaging are handled. Compare whether one environment can produce macOS, Windows, and Linux binaries while preserving the required ffmpeg builds; done means the separate pipelines can be reduced without breaking packaging or Go version pinning.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system, ci-cd
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.