this post was submitted on 15 Apr 2025
23 points (96.0% liked)
Programming
19656 readers
395 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think that's accurate, the post is from seven years ago. Additionally there are a lot of materials online that indicate your still can - https://virtualizare.net/devops/how-to-run-gitlab-runner-locally-best-practices.html
I think there is a misunderstanding, what running locally means.
You can run a gitlab runner on your local machine, but it needs to pulls it's jobs from git. It also requires gitlab to register your runner, so it can't really work for new contributors to use themselves.
Ahh, I see what you mean.
At that point I feel like you may as well just use makefiles. Did that at an old company, it had params for local deployment testing vs CICD. This also let's you define how you break the local deployment tests, as usually you can't really fully test a CICD locally.