A similar problem mentions a workaround:
it may be useful to note that it will and will not work to add gitlab-ci-runner.
I managed to get this to work by creating a new user and creating gitlab-ci-runner
with this.
I used to try to add a runner that was running under an existing user after using this main user ssh key (which was also added to my account in my gitlabhq instance).
Then I tried it using the key just generated, used only for gitlab-ci-runner.
This is a bit like issue 204 , where the problem exists for both Add and Assign to All, with the potential to call:
I think my problem is that I tried to add my key when it already existed in the project ... I can successfully add new keys just fine.
As question 207 mentions:
The runner must be registered at the GItLab CI URL. not GitLab (i.e. use http://ci.gitlab.org )
Make sure your version of gitlab-ci at least includes commit 9aca33e (from your question this should be so).
source share