-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom github runners (and arm64) #614
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much! This is looking great, just a couple comments.
Thank you! I'm going to do some testing, but this looks good. A couple minor requests:
|
@mistydemeo Updated. Also added a test, but not sure if done correctly. I also tried updating snapshots, but it changed like almost all of them... |
@mistydemeo Got the test working. |
Great, thank you! I'll do some testing and then merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Awesome 👏 |
This has landed in the 0.6.0 prereleases, which are ready to try now, and will be in the final 0.6.0 release. |
Indirectly implements: #324
I really need linux arm64 support soon, so I thought I would give this a shot.
I originally had a setting like
arm64-linux-runner
that I would use for linux arm64 triples, but it felt very restrictive. Instead, I went with acustom-runners
map, that allows any triple to define the runner it wants to use. This is nice.Working in plan/manifest: