You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some keys, perhaps just the locked key for use in the gitlab-runner register step, are misinterpreted by the ruby CLI library. Despite the fact the Gitlab team say they have fixed this as of version 10.0.2, it appears that it's not working correctly.
What behaviour did you expect instead
Expecting to be able to create ci runners in an unsupervised fashion that are fully functional.
Output log
Notice: /Stage[main]/Gitlab::Cirunner/Gitlab::Runner[teng4317-gitlabci-docker-c534]/Exec[Register_runner_teng4317-gitlabci-docker-c534]/returns: PANIC: The url needs to be entered
I've cloned this repository, and haven't done extensive testing, but it appears to be working as expected with a minor adjustment to the runner.pp manifest:
# Convert configuration into a string
$parameters_array = join_keys_to_values($_config, '=') # adding the '=' allows this to function.
$parameters_array_dashes = prefix($parameters_array, '--')
$parameters_string = join($parameters_array_dashes, ' ')
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Some keys, perhaps just the
locked
key for use in thegitlab-runner register
step, are misinterpreted by the ruby CLI library. Despite the fact the Gitlab team say they have fixed this as of version 10.0.2, it appears that it's not working correctly.What behaviour did you expect instead
Expecting to be able to create ci runners in an unsupervised fashion that are fully functional.
Output log
Any additional information you'd like to impart
The suggestion was to use
--key=value
formatting in this closed issue https://gitlab.com/gitlab-org/gitlab-runner/issues/2782I've cloned this repository, and haven't done extensive testing, but it appears to be working as expected with a minor adjustment to the
runner.pp
manifest:The text was updated successfully, but these errors were encountered: