Define CI Testing Matrix and Build Artifacts

[mormj]

CI Matrix / Build Artifact Discussion

Putting this here for initial discussion for defining GR4 CI coverage, supported toolchains, and build artifacts and trying to get ideas and open questions written down, with the goal of simplifying the current CI process and keeping scope to the target users

Initial CI Matrix Ideas

Linux

• Ubuntu 24.04

  • GCC 14
  • GCC 15
  • Clang 20

• Ubuntu 26.04

  • GCC 15
  • GCC 16

• Fedora 44

  • Clang

macOS

• latest macOS runner
  • Homebrew llvm@22

WASM

• Emscripten

---

Possible CI Dimensions

Not every environment necessarily needs all of these.

• Debug + Release
• ASan
• UBSan
• Unit tests
• Runtime/integration tests
• WASM/browser smoke tests
• Studio frontend tests
• SIMD enabled vs portable builds

---

Build Artifacts

Docker Images

• gr4-sdk

Possible future images:

• gr4-runtime
• gr4-dev
• gr4-wasm-sdk

---

Things We Probably Need To Decide

PR vs Nightly Coverage

Probably makes sense to split:

• fast PR validation
• broader nightly or merge to main coverage

Question is where that split should be.

Sanitizers

Which ones and when to run

ARM64

Feels increasingly important, especially for:

• Apple Silicon devs
• embedded deployments

macOS Coverage

Questions:

• use Apple clang at all, or standardize on Homebrew LLVM?

WASM

Questions:

• What does the build artifact look like

Artifacts / Publishing

Questions:

• publish containers on every merge or only releases?
• eventually .deb packages?
• Homebrew tap eventually?