Make CI for self-hosted M1 a little more reproducible

[samscott89]

We currently do tests of m1 builds by running self-hosted runners on m1 machines (e.g. my laptop).

I had to do this recently, and here were the steps I did to get it working:

• Followed the instructions here: https://github.com/osohq/oso/settings/actions/runners/new. This was easy. Make sure it has the m1 tag though
• Installed python3.8 -> python 3.10 (brew install python@3.8), and then make sure /opt/homebrew/opt/python@3.8/bin/python3 exists, i had to symlink for 3.8 and 3.9
• Installed go 1.16, go.1.17 (brew install go@1.16), and then symlink the binaries to ~/go/bin/go1.16 etc.

[kkirsche]

Worth keeping an eye on actions/runner-images#2187 which is downstream of github/roadmap#528 also as if they add support upstream, that'll be easier than self-hosted alternatives

Currently marked as:

ankneis moved this from Future to Q3 2023 – Jul-Sep in GitHub public roadmap github/roadmap#528 (comment)