> most of the new core infrastructure that Arm is deploying is on proprietary hardware GitHub offers self-hosted CI runners, but it's infamously limited. Last

> most of the new core infrastructure that Arm is deploying is on proprietary hardware GitHub offers self-hosted CI runners, but it's infamously limited. Last I checked there's still no official GH runner release for arm64-darwin (for which community, including yours truly, provided reliable workarounds through Rosetta that still lands you in an arm64-darwin bash, and now IIUC actual native builds[1]), there's no way to select anything else than x64 in the UI for Windows and macOS, which sets some tags on the runners that you can't remove, and there's no way to say "Other" with a custom value. Comparatively, gitlab-runner is a crazy adaptable piece of code, that allows for quite unique setups[0], combined with the loose way one can automatically assign jobs to runners using tags GL pipelines trounce GHA workflows†. [0]: https://docs.gitlab.com/runner/executors/ https://docs.gitlab.com/runner/executors/ [1]: https://github.com/actions/runner/issues/805 https://github.com/actions/runner/issues/805 † GHA covers 80% of cases (from basic to a bit more involved) somewhat nicely, but when it starts to fall short it's terrible. > A large bonus for Arm was that GitLab is open source and the company wanted to use its own tools to support its open source ecosystem. > minimize vendor lock-in > Because Arm is an IP company, security is paramount When GNU-ish philosophy meets business requirements. GitHub can be self-hosted (at a price!) but GitLab is FOSS, so it can be audited, and if necessary, forked. From code to data, it can be owned, end to end.