Comment by tempodox

7 months ago

> You generally can't run them locally

GitLab CI gives you local runners. You can completely self-host CI.

9 comments

tempodox

Reply
Plasmoid  7 months ago

It's not self hosting. It's can I run the build from my local command line and get the same results.

  • tempodox  7 months ago

    How is running those runners on our own hosts (locally) not self-hosting?

    • mdaniel  7 months ago

      Spoken like someone who has not tried what you are describing. There are two moving parts to your response: a locally hosted runner awaits jobs from GitLab itself, which doesn't help running _locally_, and the other part is that -- back when it existed! -- trying $(gitlab-runner exec) was not a full fledged implementation of the GitLab CI concepts, making it the uncanny valley of "run something locally."

      However, as of v16 there is no more exec https://gitlab.com/gitlab-org/gitlab/-/issues/385235 which I guess is good and bad. Good in that it not longer sets improper expectations that it could have plausibly done anything, and bad in that now it joins GitHub Actions[1] in not having any _local_ test strategy aside from "boot up gitlab/gitlab-ce && echo good luck"

      1: yes, I'm acutely aware of the 3(?) implementations/forks of nektos/act that claim to do GHA but, again, readme is not software and I can tell you with the utmost certainty they do not do as advertised

      1 reply →

Joker_vD  7 months ago

Well, yes, but aren't those runners have different configuration than the runners that are actually deployed and used by your company's CI/CD?