We migrated from a private BuildBot setup to GitHub Actions for all our CI needs maybe 8 or 9 months ago. While most things work great the stability on macOS is far from great. Example:
Today I ran the actions/setup-java task to setup java on macOS-latest and was greeted by: ##[error]getaddrinfo ENOTFOUND static.azul.com. Some kind of network issue on the macOS runner?
We have previously also reported that macOS runners fail to start (error provisioning resources).
I really don’t feel that it is reasonable for the macOS builds to cost the most (10 times more expensive than jobs running on Linux) when the stability is sub-par. And while it is possible to do most of the steps of a job on Linux it is not possible to do all steps. Code signing and notarization still has to happen on macOS. And the notarization step is usually the last one in a chain of steps. Having the last step fail due to stability issues with the service itself is down-right infuriating.
And before you say that GitHub Actions is free on public repositories I also want to point out that we have jobs depending on macOS in private repos which we can’t make public for legal reasons.