GitLab Runner uses the Go
to detect the underlying OS and eventually install the service file based on
the init system.
serviceinstalls, un-installs, starts, stops, and runs a program as a service (daemon). Windows XP+, Linux/(systemd | Upstart | SysV), and macOS/Launchd are supported.
When GitLab Runner is installed, the service file is automatically created:
In some cases, you might want to override the default behavior of the service.
For example, when you upgrade GitLab Runner, you should stop it gracefully until all running jobs are finished. However, systemd, upstart, or other services may almost immediately restart the process without even noticing.
So, when you upgrade GitLab Runner, the installation script kills and restarts the runner process that was probably handling new jobs at the time.
For runners that use systemd, create
/etc/systemd/system/gitlab-runner.service.d/kill.conf with the following
[Service] TimeoutStopSec=7200 KillSignal=SIGQUIT
After adding these two settings to the systemd unit configuration, you can
stop the runner and systemd uses
SIGQUIT as the kill signal, to stop the
process. Additionally, a 2h timeout is set for the stop command, which
means that if any jobs don’t terminate gracefully before this timeout, systemd
kills the process by using
For runners that use upstart create
/etc/init/gitlab-runner.override with the
kill signal SIGQUIT kill timeout 7200
After adding these two settings to the upstart unit configuration, you can stop the runner and upstart does exactly the same as systemd above.