Replies: 2 comments
-
Currently, Github allows M1 jobs natively. No more reasons to use FlyCI |
Beta Was this translation helpful? Give feedback.
0 replies
-
BUT the GH M1 runners need to be tested with a compiled project to assure we don't need the M2 runners from FlyCI |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are currently using the Starter plan on FlyCI, for M2 builds.
This plan gives us 500 minutes per month free and $0.06 per minute thereafter for projects within
EasyScience
organization.We are allowed to run 5 concurrent jobs, which should be enough for our projects, at least for a while.
However, we should limit the usage of
flyci-macos-14-m2
runners to cases where it is necessary.The cases include:
develop
and tomaster
master
Any other cases we should thing about?
Beta Was this translation helpful? Give feedback.
All reactions