Skip to content

Log fatal error when concurrent is less than 1

Tomasz Maczukin requested to merge improvement/log-warning-when-concurrent-is-zero into master

What does this MR do?

Adds a log entry printed when concurrent = 0 and no jobs are processed:

Starting multi-runner from /etc/gitlab-runner/config.toml ...  builds=0
Running in system-mode.

Configuration loaded                                builds=0
Metrics server disabled
FATAL: Concurrent is less than 1 - no jobs will be processed

Why was this MR needed?

When concurrent will be set to 0, then Runner does nothing. The process is running, but no job is processed and no message is printed in logs. This may confuse users (#2107 (closed)).

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Closes #2107 (closed)

Merge request reports