Skip to content
代码片段 群组 项目
未验证 提交 0a3d61b1 编辑于 作者: Pedro Pombeiro's avatar Pedro Pombeiro 提交者: GitLab
浏览文件

Merge branch '411917-hide-legacy-ui-based-on-app-namespace-setting' into 'master'

Add documentation on disabled runner registration token

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148942



Merged-by: default avatarPedro Pombeiro <noreply@pedro.pombei.ro>
Reviewed-by: default avatarFiona Neill <fneill@gitlab.com>
Co-authored-by: default avatarfneill <fneill@gitlab.com>
Co-authored-by: default avatarMiguel Rincon <mrincon@gitlab.com>
No related branches found
No related tags found
1 合并请求!2419Fix TanukiBot spec relying on outdated code
...@@ -42,6 +42,23 @@ You can set all new projects to have instance runners available by default. ...@@ -42,6 +42,23 @@ You can set all new projects to have instance runners available by default.
Any time a new project is created, the instance runners are available. Any time a new project is created, the instance runners are available.
## Enable runner registrations tokens
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147559) in GitLab 17.0
WARNING:
The ability to pass a runner registration token, and support for certain configuration arguments was deprecated in GitLab 15.6 and will be removed in GitLab 18.0. Runner authentication tokens should be used instead. For more information, see [Migrating to the new runner registration workflow](../../ci/runners/new_creation_workflow.md).
In GitLab 17.0, the use of runner registration tokens to create runners was disabled in all GitLab instances.
Users must use runner authentication tokens instead.
If you have not yet [migrated to the use of runner authentication tokens](../../ci/runners/new_creation_workflow.md),
you can enable runner registration tokens. This setting and support for runner registration tokens will be removed in GitLab 18.0.
1. On the left sidebar, at the bottom, select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
1. Select the **Allow runner registration token** checkbox.
## Instance runners compute quota ## Instance runners compute quota
As an administrator you can set either a global or namespace-specific As an administrator you can set either a global or namespace-specific
......
...@@ -81,6 +81,7 @@ should be used instead. For more information, see [Migrating to the new runner r ...@@ -81,6 +81,7 @@ should be used instead. For more information, see [Migrating to the new runner r
Prerequisites: Prerequisites:
- Runner registration tokens must be [enabled](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the Admin Area.
- You must be an administrator. - You must be an administrator.
To create an instance runner: To create an instance runner:
...@@ -275,7 +276,10 @@ The ability to pass a runner registration token, and support for certain configu ...@@ -275,7 +276,10 @@ The ability to pass a runner registration token, and support for certain configu
[deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/380872) in GitLab 15.6 and will be removed in GitLab 18.0. Authentication tokens [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/380872) in GitLab 15.6 and will be removed in GitLab 18.0. Authentication tokens
should be used instead. For more information, see [Migrating to the new runner registration workflow](new_creation_workflow.md). should be used instead. For more information, see [Migrating to the new runner registration workflow](new_creation_workflow.md).
You must have the Owner role for the group. Prerequisites:
- Runner registration tokens must be [enabled](#enable-use-of-runner-registration-tokens-in-projects-and-groups) in the top-level group.
- You must have the Owner role for the group.
To create a group runner: To create a group runner:
...@@ -473,6 +477,7 @@ should be used instead. For more information, see [Migrating to the new runner r ...@@ -473,6 +477,7 @@ should be used instead. For more information, see [Migrating to the new runner r
Prerequisites: Prerequisites:
- Runner registration tokens must be [enabled](#enable-use-of-runner-registration-tokens-in-projects-and-groups) in the top-level group.
- You must have at least the Maintainer role for the project. - You must have at least the Maintainer role for the project.
To create a project runner: To create a project runner:
...@@ -664,3 +669,24 @@ project. ...@@ -664,3 +669,24 @@ project.
1. Select the runner name and find the **IP Address** row. 1. Select the runner name and find the **IP Address** row.
![Project runner IP address](img/project_runner_ip_address.png) ![Project runner IP address](img/project_runner_ip_address.png)
## Enable use of runner registration tokens in projects and groups
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148557) in GitLab 17.0
WARNING:
The ability to pass a runner registration token, and support for certain configuration arguments was deprecated in GitLab 15.6 and will be removed in GitLab 18.0. Runner authentication tokens should be used instead. For more information, see [Migrating to the new runner registration workflow](../../ci/runners/new_creation_workflow.md).
In GitLab 17.0, the use of runner registration tokens to create runners was disabled in all GitLab instances.
Users must use runner authentication tokens instead.
If you have not yet [migrated to the use of runner authentication tokens](../../ci/runners/new_creation_workflow.md),
you can enable runner registration tokens for projects and groups. This setting and support for runner registration tokens will be removed in GitLab 18.0.
Prerequisites:
- Runner registration tokens must be [enabled](../../administration/settings/continuous_integration.md#enable-runner-registrations-tokens) in the Admin Area.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
1. Turn on the **Allow members of projects and groups to create runners with runner registration tokens** toggle.
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册