Ruby runner recipe registration#
When this error occurs, the first step is to ask a GitLab administrator to verify that the registration token is valid.Īdditionally, confirm that runner registration in the project or group is allowed by the GitLab administrator. Has been changed in GitLab or when the user did not correctly enter the registration token. This issue can occur when the instance group or project registration token The check registration token error message is displayed when the GitLab instance does not recognize The maximum allowed length is 255 characters. You can use it to add information related to runner maintenance. The -maintenance-note parameter was added in GitLab Runner 14.8. This value can later be toggled on or off in the project’s Settings > CI/CD menu. Use this parameter during registration to create a protected runner.įor a protected runner, use the -access-level="ref_protected" parameter.įor an unprotected runner, use -access-level="not_protected" instead or leave the value undefined. It uses a registration API parameter introduced in GitLab 11.11.
The -access-level parameter was added in GitLab Runner 12.0. Docker run -rm -v /srv/gitlab-runner/config:/etc/gitlab-runner gitlab/gitlab-runner register \ -non-interactive \ -executor "docker" \ -docker-image alpine:latest \ -url "" \ -registration-token "PROJECT_REGISTRATION_TOKEN" \ -description "docker-runner" \ -maintenance-note "Free-form maintainer notes about this runner" \ -tag-list "docker,aws" \ -run-untagged = "true" \ -locked = "false" \ -access-level = "not_protected"
0 kommentar(er)
