Request: Support Windows on Arm64

[johnnyshields]

Ruby recently added support for windows-arm64.

The Ruby Installer team would like to support Windows on Arm64 as well, but the current ticket is blocked due to lack of setup-ruby support for windows-arm

Therefore, I would like to request support. Unfortunately Github is not providing Windows ARM runners out-of-the-box. My company TableCheck would be happy to provide self-hosted Windows ARM runners until Github gives official support if it helps.

[MSP-Greg]

provide self-hosted Windows ARM runners

I know nothing about Windows on Arm64.

Do any current Actions Windows images run on Arm64? setup-ruby requires node.js.

Regardless, I'll have a look at what MSYS2 has available.

[eregon]

Can you use setup-ruby in self-hosted mode then? Just use it and follow the steps it mentions in the error.

I don't think much more support is realistic for a platform without official runners.

[johnnyshields]

Issue for Github runners: actions/runner-images#768

[eregon]

I forgot, Windows is a bit special, setup-ruby uses RubyInstaller, like the README says.
https://rubyinstaller.org/downloads/ does not seem to have arm64 builds, so that needs to happen first (feel free to file an issue there).
Once that is done I think we could support windows arm64 easily in setup-ruby, whether self hosted or not because those builds should work in either case (EDIT: though the windows toolchain stuff needs to be adapted too, and not sure how well that would work in self hosted).

[eregon]

So that's oneclick/rubyinstaller2#362 and that's blocking this issue.

[johnnyshields]

OK @eregon thank you for the clarification!

[eregon]

Thinking more about this, this issue is blocked by two things:

• RubyInstaller2 builds of CRuby on windows-arm64 (Add installer for windows-arm64 oneclick/rubyinstaller2#362)
• Having a GitHub-hosted runners for windows-arm64 to be able to test and avoid regressions.

I thought originally the second point might be less important if we are "just using RubyInstaller2 builds", but that's not the case, the windows toolchain stuff also needs to be done and that should be tested properly.
Also in general support setup-ruby does not support any version/platform it cannot test.

So I will close this issue for now, and we can reopen it when both these blockers are resolved.

---

My company TableCheck would be happy to provide self-hosted Windows ARM runners until Github gives official support if it helps.

This wouldn't work unfortunately, there are several concerns with that:

• What if those custom Windows ARM runners are running a different Windows version vs what other users use?
  Or what if those runners have some software installed/configured differently which means it works there but not in other places?
  For example the current windows toolchain stuff does need to assume things about where git and openssl and MSYS2 packages are installed and which versions, etc.
• If the builds are done on these runners (would be a concern for Add installer for windows-arm64 oneclick/rubyinstaller2#362 I'd think and for building the windows toolchain stuff), there is a security concern that anything compromised on these runners (e.g. a bad gcc installed by some virus) could end up in the resulting CRuby build, which could result in affecting any user of these builds.
• These runners might have a different CPU, and some of the compilation might be CPU-features specific.