-
Notifications
You must be signed in to change notification settings - Fork 32
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
Regression tests on Github actions #113
Comments
Hi @pvelissariou1 |
@pvelissariou1 Here is reference to @SorooshMani-NOAA communications: Github repo to look at: |
Closed. Github with current limitations is not ready for the task. Will move to:
|
Hi Takis,
Based on the number of users would you please provide an estimate for the
year. Can we guess how many tests we need to perform and so on?
Thanks,
-Saeed
…______________________________________________________
Saeed Moghimi, PhD
*NOS Storm Surge Modeling
<https://nauticalcharts.noaa.gov/learn/storm-surge-modeling.html> Team Lead*
Coastal Marine Modeling Branch, Coast Survey Development Laboratory, Office
of Coast Survey at NOAA National Ocean Service.
Address: 1315 East West Hwy, Room 6607, Silver Spring, Maryland 20910
Phone: (302) 827-3986
The contents of this message are mine personally and do not necessarily
reflect any position of NOAA.
On Tue, Jun 28, 2022 at 12:58 PM Panagiotis Velissariou < ***@***.***> wrote:
Assigned #113 <#113>
to @saeed-moghimi-noaa <https://github.com/saeed-moghimi-noaa>.
—
Reply to this email directly, view it on GitHub
<#113 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APZULD42RDD5NNQP6LFO5Q3VRMVMPANCNFSM52C3X6HA>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Option #1: It seems that the most flexible option for CMMB repos is to use "self hosted runners". This option will require the setup/configuration of a physical/virtual Linux machine with the docker software installed. We might need minimum 8 cores and about 64 GB memory.
This option gives us the flexibility to maintain both the runner machine as well as the container.
The current limit of cpus in (free) github actions for Linux/Windows is 2.
NOTE: we can maintain a Linux VM on the cloud (best approach I think).
Option #2: The other option is paid subscription (using codebase) that provides up to 32 cores. Need to upgrade to non-free organization setup for GitHub. Depending on the configuration of the GitHub organization the charges range: $4-$44 per year/per user. The use of resources cpus/memory is about $0.18/hour (Linux/Windows)
The text was updated successfully, but these errors were encountered: