Skip to content

CI: Add RISC-V runner support and matrix-based workflow#1

Closed
whileone-sk wants to merge 5 commits intoFFmpeg:masterfrom
Whileone-Techsoft:ci-riscv64-runner
Closed

CI: Add RISC-V runner support and matrix-based workflow#1
whileone-sk wants to merge 5 commits intoFFmpeg:masterfrom
Whileone-Techsoft:ci-riscv64-runner

Conversation

@whileone-sk
Copy link
Copy Markdown

This PR updates the GitHub Actions CI workflow to support RISC-V builds
using a matrix-driven runner setup.

Key changes:

  • Introduces riscv64 support via workflow_dispatch inputs
  • Dynamically generates job matrices based on requested runner counts
  • Reuses existing x86_64 runner registration for RISC-V (QEMU/emulation-based)
  • Keeps Windows and macOS matrices unchanged
  • Validated locally using act with a custom event.json

Notes:

  • Local-only files (event.json, act config) are committed.
  • Some cache and cleanup steps are skipped or behave differently under act

- Add logical linux-riscv64 runner label
- Register Docker-based RISC-V runner configuration
- Enable QEMU-based smoke testing on amd64 hosts
- No native RISC-V hardware required
- Add logical linux-riscv64 runner label
- Register Docker-based RISC-V runner configuration
- Enable QEMU-based smoke testing on amd64 hosts
- No native RISC-V hardware required
- Add logical linux-riscv64 runner label
- Register Docker-based RISC-V runner configuration
- Enable QEMU-based smoke testing on amd64 hosts
- No native RISC-V hardware required
@BtbN
Copy link
Copy Markdown
Member

BtbN commented Apr 6, 2026

This is not something we need or want (It'd be way to slow).
And we also won't be pulling random third party images for our CI.
Also, you're aware that this is only backend for our Forgejo CI?

@BtbN BtbN closed this Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants