debops / ansible-gitlab_runner

Manage GitLab Runner instances

gitlab_runner

GitLab Runner is a service written in Go which is used by the GitLab CI to execute software builds on remote hosts. It supports builds executed by local shell, over SSH or in a Docker containers.

The debops.gitlab_runner Ansible role will allow you to install and manage GitLab Runner on Debian and Ubuntu hosts. You can use it to create multiple Runner instances, each one with distinct configuration. The role will automatically register the Runners in GitLab CI management host if a required registration token is supplied.

Installation

This role requires at least Ansible v2.0.0. To install it, run:

ansible-galaxy install debops.gitlab_runner

Documentation

More information about debops.gitlab_runner can be found in the official debops.gitlab_runner documentation.

Are you using this as a standalone role without DebOps?

You may need to include missing roles from the DebOps common playbook into your playbook.

Try DebOps now for a complete solution to run your Debian-based infrastructure.

Authors and license

gitlab_runner role was written by:

• Maciej Delmanowski | e-mail | Twitter | GitHub

License: GPLv3

---

This role is part of the DebOps project. README generated by ansigenome.

ansible-gitlab_runner's Issues

APT Key registration failed for the default value

Hello guys, I was trying to run the role for provisioning a vagrant box. I used pretty much all the default values except obviously the gitlab token. Everything went fine till the "Add gitlab-runner APT key" task which returned a rather lengthy error "Error fetching key 1A4C919DB...".

This, I learned afterwards, was being cause by the default value for the apt_key id "hkp://pool.sks-keyservers.net".

This issue was fixed by specifying the port 80 for that URL. So, simply changing "hkp://pool.sks-keyservers.net" for "hkp://pool.sks-keyservers.net:80" in the id argument (line 56 of tasks/main.yml) fixed the problem for me.

Support GitLab 10

Hi,

first of all thanks for this great ansible role.

Currently this role uses api version v1 to manage runners, but in GitLab 10 this api version is not supported anymore. Current version is v4: https://docs.gitlab.com/ce/api/runners.html

Is there any plan to update to this version?

Greetz,
David

default shell runner registration is skipped

TASK [debops.gitlab_runner : Check if GitLab service is available] ******************************************************************************************************************************
ok: [scw-0783ca]

TASK [debops.gitlab_runner : Register new GitLab Runners] ***************************************************************************************************************************************
skipping: [scw-0783ca] => (item={u'name': u'scw-0783ca', u'executor': u'shell'})

My playbook uses the gitlab_runner role straight out of the box, with little cofiguration except to provide the Gitlab CI token.

Archive this repository

I've seen this repository is still presents on https://galaxy.ansible.com/debops/

Any reason ? Because we have a dedicated gitlab_runner role in current collection.

Distributed Cache Bucket Location configuration key

To use the distributed cache functionality with (I'm assuming) a non-us-east-1 region you need to configure the bucket location.

https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnerscache-section

OffPeak* parameters DEPRECATED with 14+ version gitlab-runner

With version 14+ gitlab-runner deprecated parameters OffPeak - https://docs.gitlab.com/runner/configuration/autoscale.html#off-peak-time-mode-configuration-deprecated

gitlab-ci-multi-runner was renamed to gitlab-runner

Hi @drybjed

the project gitlab-ci-multi-runner was renamed to gitlab-runner and so also the package with version 10: https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/661

Of course I could just change the gitlab_runner__base_packages and gitlab_runner__apt_repo and do the pre-upgrade steps by my own. But maybe you want to add an option to upgrade to version 10? However, I just want to let you know that it was renamed :)

Best,
David

500 errors while registering runners

I seem to be getting 500 errors somewhat randomly when I am running a playbook with serial: +1 (multiple runners are getting configured at the same time since it is running the tasks in parallel). I am not sure how prevalent it is, but I have seen it at least a few times with my GitLab instances though it is solved by just re-running the playbook.

Would be make sense to add some retry/wait logic around registering with GitLab or would it be better to just deal with it at the playbook level?