-
Notifications
You must be signed in to change notification settings - Fork 6
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
Spending money on GitHub actions: what would be the scale? #20
Comments
FWIW, input here. Please consider in your budgeting exercise that the project should be able to grow and more contributions & support for more platforms means more PRs, means more CI resources. For OQS our goal has been to stay "lean and mean"/ecologically responsible (e.g., to test some platforms only in downstream sub projects as opposed to every sub project or do do weekly tests instead of "merge-at-main" CI, etc.) -- but this required work and discipline that someone needs to provide also going forward. |
Yup. My hope is that with the exception of ARM runners, we are able to keep PQCA on the free plan at GitHub. |
Within PQCP we have some requirements from the arm implementations to use AWS. I don't believe github arm runners meet their requirements. More details at https://github.com/pq-code-package/mlkem-c-aarch64/issues/34 |
This has been approved by the governing board. |
Please share any additional details on this topic
OQS has requested the ability to run ARM builds on GitHub. The first step of this is having a budget estimated so it can be requested; the second step is to get the orgs into the ARM runner beta.
Detail what actions or feedback you would like from the TAC
An estimated spend and decision on how broadly this should be used. I don't know how much, if anything, is spent at CircleCI, for comparison.
How much time do you need for this topic?
5 minutes or less
The text was updated successfully, but these errors were encountered: