Static Runner’s managed by Gitlab

Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Static Runner’s provided by Gitlab.

i.e Gitlab Offered Runner’s which are static and available all the time.

Steps to reproduce

N/A

Configuration

Static Gitlab Managed Runners

Versions

Please select whether options apply, and add the version information.

• Self-managed
• [yes ] GitLab.com SaaS

Versions

• GitLab (Web: /help or self-managed system information):

Helpful resources

1. Before opening a new topic, make sure to search for keywords in the forum search
2. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
3. Troubleshooting docs: Self-managed GitLab instances.

Thanks for taking the time to be thorough in your request, it really helps!

Once we run job, it should pick available runners provided by Gitlab. Rather than spinning up runnner’s dynamically. As I wants to have a static runner’s let’s say 5, which should be available all the times.

I am aware of self-managed runner’s, but the idea here is to see whether Gitlab is offering such runners.

@manuelgrabowski Appreciate your feedback/inputs on this.

Hey @shaikzoheb – this is not something we currently offer. Looking at the direction page for our SaaS Runners it does look like some of our future plans should align with what you’re looking for (emphasis mine):

Our flagship offering will be custom-hosted runners, allowing users to create custom GitLab-hosted runners via GitLab UI, fully dedicated to their project, with more advanced features such as dedicated IP-range, or SSH access for debugging.

@manuelgrabowski Thanks for sharing the details

No worries The most relevant thing for following the progress would be Custom-hosted runners (parent epic) (&10073) · Epics · GitLab.org · GitLab