[carlosf]

I'm a paying customer and I agree.

Meanwhile many core features are still unpolished e.g.: running your own runners sucks and you can't test CI/CD locally.

[deastman]

Hi Carlos, Darren here, PM for runner. Can you provide a bit more insight in terms of some of the challenges that you are having with hosting your own runners? In regards to testing CI locally, did you mean having the ability to validate that a pipeline is fully functional prior to pushing your commit to GitLab?

[kasbah]

Not the OP but we can't enable our self-hosted runner on our open source project because if we do then the pipeline won't run on external merge requests. It simply fails with permission errors when we get merge requests. So we have to use the shared runners which are less powerful.

[deastman]

ok ping me on the epic link below. @DarrenEastman is the GitLab handle and let me know what compute class you are needing. We are planning to pivot soon on getting various compute types available on GitLab.com Shared runners.

https://gitlab.com/groups/gitlab-org/-/epics/2426

[fuzzy2]

Hm? Actually you can indeed test CI locally, if only one step at a time. This is a very very rare feature. It’s gitlab-runner exec.

Also, I find that running your own runner is super easy and straightforward.

[jamietanna]

What do you mean re not testing locally? I've had good success with hosting a runner on my local machine and using it to run the jobs