Allow Self-Managed Instances access to GitLab hosted runners
Problem to solve
Self-managed customers are choosing non-GitLab SaaS hosted CI, we should have options for them to utilize GitLab hosted CI.
Target audience
Self-managed infrastructure operators who are required to and are comfortable setting up low elasticity infrastructure for hosting GitLab but want to avoid (for operational burden or cost) the management of high elasticity compute infrastructure needed to cover their CI needs.
Further details
Use Cases
- As Sidney I should be able to have my instance or selected groups and projects utilize GitLab's shared runner CIs
- As Sidney I should be able to have my instance or selected groups and projects utilize dedicated runners created and hosted for that purpose by GitLab
Proposal
Create the ability to, and ensure adequate performance of, connecting self-managed instances to GitLab's shared runner CIs. Create the ability to, and ensure adequate performance of, creating dedicated runners deployed and operated by GitLab and connected to self-managed instances
What does success look like, and how can we measure that?
3% SMAU in CI after six months of launch as self-managed customers move from other SaaS CI providers.