gitlab-runner register should allow to define concurrent value
Overview
When a user run gitlab-runner register
they have no option to define the concurrent
value inside the config.toml file inside of the global section. This leads into users have to edit the file manually or having some kind of script to change it later on.
Proposal
New files
Add a flag/env variable to gitlab-runner register
where the user can define the concurrency value, and it will be saved in the newly created config.toml
file
Reusing the config file
You can run gitlab-runner register
and the config.toml
file already exists. At this point, if the concurrency is specified it should be ignored, we shouldn't handle this case in a separate issue but introducing some new command to update the global section only.
Original request
I suppose this is a feature request unless I'm missing the option, this is based on; https://forum.gitlab.com/t/gitlab-runner-register-set-concurrency/3784
It appears that gitlab-runner register doesn't have a command line switch to define the number of concurrent builds in the /etc/gitlab-runner/config.toml (Concurrent = XY). For those of us that auto-scale our gitlab-runners with upstart/kickstart scripts this would be a very helpful addition. Right now I need to either completely generate the config.toml, manually edit it on each server (which goes away once they're scaled up/down) or copy the file from s3 into the docker container each time a server is added.
Thanks!
First time contributors who are interested in working on this issue can contact: @steveazz