New runner registration flow
What does this MR do and why?
Add support for our E2E system to use the new runner registration flow: https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html
The new flow creates a runner through this api https://docs.gitlab.com/ee/api/users.html#create-a-runner-linked-to-a-user, and uses a runner authentication token instead of registration token. There are changes to the gitlab-runner register
command as well.
Runner registration tokens are being deprecated in 17.0 and currently scheduled for May 6-8: gitlab-com/Product#13310 (closed).
This change relates to gitlab-org/quality/quality-engineering/team-tasks#1726 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
-
Update gitlab_runner.rb
to support both old and new runner registration flow -
Create new user_runners.rb
to use the new api for creating runners -
Update gitlab_runner_spec.rb
respective to above -
Use the new flow in one test
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.