Yes, but if you put concurrent = 1 at the top of /etc/gitlab-runner/config.toml on the runner server, it should only run one job across all the defined runners (the definitions).
The only thing you should need to do twice is the gitlab-runner register ...-command (ont time against gitlab.com and one time against the server for work)
Yes, but if you put concurrent = 1 at the top of /etc/gitlab-runner/config.toml on the runner server, it should only run one job across all the defined runners (the definitions).
It’s for creating two runners (like you suspected you needed to, as you seem to know how to do it, apart from the url and the token it’s same command). But only run jobs from one GitLab server (I took a guess and guesses that was why you hesitated in just trying to register your runner against two GitLab servers - if I was wrong, you can just ignore that part).