Generate runner tokens
To register a runner, you can use either:
- An authentication token assigned to the runner when you create the runner in the UI. The runner uses the token to authenticate with GitLab when picking up jobs from the job queue.
- A registration token (deprecated).
Generate an authentication token
Registration with an authentication token is available for all runners.
The token only displays in the UI for a short period of time during registration.
For a shared runner
Version history
-
Introduced in GitLab 15.10. Deployed behind the
create_runner_workflow_for_admin
flag - Enabled by default in GitLab 16.0.
On self-managed GitLab, by default this feature is available. To hide the feature,
ask an administrator to disable the feature flag named
create_runner_workflow_for_admin
.Prerequisites:
- You must be an administrator.
To generate an authentication token for a shared runner:
- On the top bar, select Main menu > Admin.
- On the left sidebar, select CI/CD > Runners.
- Select New instance runner.
- Select a platform.
- Optional. Enter configurations for the runner.
- Select Submit.
- Follow the instructions to register the runner from the command line.
For a group runner
Version history
-
Introduced in GitLab 15.10. Deployed behind the
create_runner_workflow_for_namespace
flag. Disabled by default. - Enabled by default in GitLab 16.0.
On self-managed GitLab, by default this feature is available. To hide the feature,
ask an administrator to disable the feature flag named
create_runner_workflow_for_namespace
.Prerequisites:
- You must have the Owner role for the group.
To generate an authentication token for a group runner:
- On the top bar, select Main menu > Groups and find your group.
- On the left sidebar, select CI/CD > Runners.
- Select New group runner.
- Select a platform.
- Optional. Enter configurations for the runner.
- Select Submit.
- Follow the instructions to register the runner from the command line.
For a project runner
Version history
-
Introduced in GitLab 15.10. Deployed behind the
create_runner_workflow_for_namespace
flag. Disabled by default. - Enabled by default in GitLab 16.0.
On self-managed GitLab, by default this feature is available. To hide the feature,
ask an administrator to disable the feature flag named
create_runner_workflow_for_namespace
.Prerequisites:
- You must have the Maintainer role for the project.
To generate an authentication token for a project runner:
- On the top bar, select Main menu > Projects and find your project.
- On the left sidebar, select Settings > CI/CD.
- Select New project runner.
- Select a platform.
- Optional. Enter configurations for the runner.
- Select Submit.
- Follow the instructions to register the runner from the command line.
Generate a registration token (deprecated)
The ability to pass a runner registration token, and support for certain configuration arguments was
deprecated in GitLab 15.6. Authentication tokens
should be used instead to register runners. Registration tokens, and support for certain configuration arguments
will be disabled behind a feature flag in GitLab 16.6 and removed in GitLab 17.0. The configuration arguments disabled for
glrt-
tokens are --locked
, --access-level
, --run-untagged
, --maximum-timeout
, --paused
, --tag-list
, and --maintenance-note
. This change is a breaking
change.For a shared runner
- On the top bar, select Main menu > Admin.
- On the left sidebar, select CI/CD > Runners.
- Select Register an instance runner.
- Copy the registration token.
For a group runner
- On the top bar, select Main menu > Groups and find your group.
- On the left sidebar, select CI/CD > Runners.
- Copy the registration token.
For a project runner
- On the top bar, select Main menu > Projects and find your project.
- On the left sidebar, select Settings > CI/CD.
- Expand the Runners section.
- Copy the registration token.