Description
xref #46493 (comment)
I'm assuming it'd make our life easier, if we could significantly increase our resources in GitHub actions, so we could standardize most of our CI to use it. In partiicular builds in Azure pipelines, I think we want to keep CircleCI unless GitHub actions start supporting arm.
I contacted the open source program manager at GitHub to see if this is an option. I asked them few times already over the past few years, as part of a GitHub feedback group I'm in, but never got an answer. Let's see if this changed.
If this is not an option, I think another option could be to use a self-hosted runner. We should be able to get the hardware for free, with the sponsoring agreements we're working on at NumFOCUS. I guess it wouldn't be too complex to setup or maintain. So, maybe worth if this is going to save us time from maintaining different CI systems.
I need to check in detail, and make sure we can use both our current quota, plus self-hosted runners, but I assume it's possible.
Thoughts?