Closed displayn closed 1 year ago
As part of the deprecation of the runner registration token, the run_untagged
field will be removed from the API. This functionality can now be controlled in the GitLab Admin UI when creating a runner. This issue should be resolved once the updated GitLab Provisioner is available. More info here: https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html
See: #23
Given @ast3150 's answer I will close this
Hey folks, GitLab Runners will always register and run with the setting
untagged
jobs set totrue
. It would be nice if the configuration block could contain the attributerun_untagged
in thecilicon.yml
to set this value during the GitLab Runner registration process [1] against the GitLab Server API[2].Here is a draft example how the config block could look like:
[1] https://github.com/traderepublic/Cilicon/blob/main/Cilicon/Provisioner/GitLab%20Runner/GitLabService.swift#L32-L34 [2] https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner