Skip to content

Enable feature flags for new runner creation

What does this MR do and why?

Enable feature flags for new runner creation 🎉

This change enables the new runner creation workflow in which users can create runners and use a runner authentication token to register them to their GitLab instance.

This eliminates the need for a registration token.

Runner creation happens in the GitLab Runners settings page for the given scope, in the context of the authenticated user, which provides traceability.

See more at: https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/#next-gitlab-runner-token-architecture

See more about our documentation at: https://docs.gitlab.com/ee/ci/runners/register_runner.html

Changelog: added

Screenshots or screen recordings

image

How to set up and validate locally

Admin area:

  1. Visit Admin -> CI/CD -> Runners
  2. Select New instance runner (e.g. http://gdk.test:3000/admin/runners/new)
  3. Follow the runner registration process

Group and Project area

  1. Visit your group's home, Group -> CI/CD -> Runners

  2. Select New group runner (e.g. http://gdk.test:3000/grou/runners/new)

  3. Follow the runner registration process

  4. Visit your project's home, Settings -> CI/CD

  5. Expand Runners, select "New project runner"

  6. Follow the runner registration process (e.g. https://gitlab.com/runner-group-test/test-project/-/settings/ci_cd)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #389269 (closed)

Edited by Miguel Rincon

Merge request reports