Srv19
Srv19

Reputation: 3608

How to set up gitlab CI runners?

I am asking the question here, because documentation didn't help me.

During runner's setup, 2 things are being asked: url of gitlab CI coordinator and registration token. I don't get what any of them should be.

As for url, it could be either url of gitlab CI web interface (ex: http://localhost:80/) ot url related to build, which is described in build's advanced properties.

Registration token could be something from documentation - but the link to it is dead (see: http://gitlab-ci-domain.com/admin/runners) or registration token from build's advanced properties.

However, when i try to supply to runner's setup url and registration token from build properties, i get access error which informs me that registration failed. Due to lack of understanding what those parameters should be, i cannot determine what is wrong.

Upvotes: 17

Views: 26759

Answers (4)

CAMD_3441
CAMD_3441

Reputation: 3154

As of GitLab Enterprise Edition 12.0.0-pre 8104b83f087

The token can be found by:

  1. Go to your gitlab project
  2. Click on Settings
  3. Click on CI/CD
  4. Click on "Expand" on the Runners section
  5. The token is under "Set up a specific Runner manually"

enter image description here

Upvotes: 2

Bryan Downing
Bryan Downing

Reputation: 15472

If you can access the settings for a project, then you can find the information in Project Settings > Runners. There should be a box under Specific Runners that has the URL and token.

EDIT: As of GitLab 9.0, this info can be found under Settings > CI//CD Pipelines (per Josh Noe)

EDIT: New location as of GitLab 9.3 (maybe earlier): Settings > Pipelines

EDIT: New location as of GitLab 10: Settings > CI / CD > Runners Settings

Upvotes: 4

Paulo Botelho
Paulo Botelho

Reputation: 322

the Url is your Gitci Url. the token you mention its in your gitlabci under "runners" next to the line:

"To register new runner you should the following registration token. With this token the runner will request a unique runner token and use that for future communication"

Upvotes: 6

Srv19
Srv19

Reputation: 3608

Apparently the only way to do that is to be admin of Gitlab your CI server deals with yourself.

I find that unreasonable, but what could be done?..

Upvotes: 1

Related Questions