-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Actions: Additional customization & security for GitHub hosted runners on GHAE (beta) #95
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
GitHub hosted runners will come in new more powerful configurations which can include more CPU cores, RAM, disk space, and specialized hardware like GPUs. You can also use a custom image or optionally enable a static Public IP for use with your firewall. GitHub hosted runners on AE will also deliver the same compliance and security standards as AE. During the beta, customers will not be billed for usage of GitHub hosted runners on GHAE.
Intended Outcome
Our current runners are static in configuration and can be limiting for more intensive or specialized workflows. These new configurations will make running more complicated workflows easier and faster. The additional security capabilities mean customers will not break the GHAE security promise by using GitHub hosted runners.
How will it work?
Specifying the class of runner in your workflow file will determine the power of the runner. More powerful runners will come with higher prices per minute. Additional controls will be available for admins to manage resources and ensure the right organizations and repositories are using the right classes of runners.
The text was updated successfully, but these errors were encountered: