FS#66374 - [gitlab-runner] Default config.toml has incorrect concurrent value

Attached to Project: Community Packages
Opened by Chris Oldwood (coldwood) - Friday, 24 April 2020, 17:34 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 25 April 2020, 21:45 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Package Name: gitlab-runner
Package version: 12.9.0-1

Description:

When the gitlab-runner package is installed it creates a default config.toml in /etc/gitlab-runner with the following contents:

concurrent = 4

The default value should be 1, which is what you get when you write to a new config.toml file during registration. The reason the default of 4 causes a problem is because you may only expect one job to run by default but it will run up to 4 concurrently which can unexpectedly corrupt or exhaust a shared resource.

Note: the example config.toml provided by GitLab at https://gitlab.com/gitlab-org/gitlab-runner/-/blob/master/config.toml.example has a concurrency of 4 because it has four separate runners configured.

Workaround:

Edit the file (manually or with sed, etc.) before registering runners.

Note: you cannot change this value at registration with "gitlab-runner register".

Steps to Reproduce:

$ pacman -S gitlab-runner
$ cat /etc/gitlab-runner/config.toml
concurrent = 4
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Saturday, 25 April 2020, 21:45 GMT
Reason for closing:  Fixed

Loading...