-
Hi All- The GitHub-host runners only support a woefully underpowered VM type. (2 cores, 7GB RAM.) I know that self-hosted runners are an option, but they’re not recommended for public projects. For large projects (like LLVM) or ones that have to build large projects, this isn’t ideal. Is there a plan to address this need? This could be by providing a secure option for self-hosted runner VMs on public repos (with shutdown and scaling support to save $$). Could also be by paying for beefier machines. Obviously, dealing with PRs from other repos would have to be controlled. ~John |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 2 replies
-
Thanks for your feedback. I recommend that you can directly share your suggestions here. That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions. In addition, you also can follow the “GitHub public roadmap” repository where you can learn about what new features the appropriate engineering teams are working on, what stage these features are in, and when the teams expect to bring them to users. |
Beta Was this translation helpful? Give feedback.
-
Hi @teqdruid, I think this is a well known use case, I suspect this future roadmap feature below may deliver what you need github.com/github/roadmapActions: Multiple hosted runner sizes (Beta)
Summary GitHub hosted runners will come in new more powerful configurations which can include more CPU cores, RAM, disk space, and...
actions
all
beta
cloud
code-to-cloud
|
Beta Was this translation helpful? Give feedback.
-
Excellent! That’s exactly what I asking about! Would this be available to public repos? How would pricing work for them? |
Beta Was this translation helpful? Give feedback.
-
@teqdruid, unfortunately the public roadmap item has moved moved to Future column so that is 3Q 2021 or later, (unless it gets moved earlier), so I would not expect much additional detail for a good while yet. I guess that leaves you with the answer of self-hosted runners, which are not recommended with public repositories for reasons already stated by GitHub, and which you have already noted. |
Beta Was this translation helpful? Give feedback.
-
Hi, did this get resolved? Can I have my GitHub hosted runners with a different machine size? 2 CPUs 7GB are not enough 😦 |
Beta Was this translation helpful? Give feedback.
-
@Jongy unfortunately current sizings are still as listed here supported-runners-and-hardware-resources I can’t see anything on the Public Roadmap for this, so its a matter of watching the roadmap and announcements and using self-hosted runners sized to your needs unless someone knows differently. I wouldn’t assume if will be a free offering if/when something is delivered. In this repository, you can find the official GitHub public feedback discussions, you could add your voice hear. |
Beta Was this translation helpful? Give feedback.
-
It looks like this is on the roadmap under:
Actions: More powerful runners choices for GitHub-managed runners on GitHub.com
**Summary** GitHub-managed runners will now include the option to choose more …powerful combinations of CPU, RAM, & disk space for your jobs. These more powerful configurations are also privately pooled on your behalf, which means you can optionally enable a static Public IP range for use with your firewall, or proxy/bastion server. Intended Outcome How will it work? |
Beta Was this translation helpful? Give feedback.
-
Any progress? |
Beta Was this translation helpful? Give feedback.
Hi @teqdruid, I think this is a well known use case, I suspect this future roadmap feature below may deliver what you need
github.com/github/roadmapActions: Multiple hosted runner sizes (Beta)