|(13 intermediate revisions by 2 users not shown)|
is an application that works with GitLab CI/ CD to run jobs in a pipeline.<ref>https:// docs. gitlab. com/ runner/ </ref> For more information see the official [https:// docs. gitlab. com/ runner/ GitLab Runner documentation] .
=== Current Gitlab Runner setup ([[ phab: T287279|T287279]] ) ===<!-- Additional information needed, feel free to edit -->
In WMCS there is a project <code>gitlab-runners</code> to host a set of shared GitLab runners. Currently the runners are installed and configured with [[ gerrit:plugins/ gitiles/operations/gitlab-ansible/| Ansible playbook]]. To add runners, add the hosts to <code>[ gitlab_runners]</code> section of 'hosts' file. Then run the Ansible Playbook for gitlab-runners. The command is wrapped in <code>[ [gerrit: plugins/ gitiles/operations/gitlab -ansible/ +/ refs/heads/master/install-gitlab-runner.sh|install-gitlab-runner.sh]]</code> script.<ref>https:// phabricator. wikimedia.org/T285913
of . [[//|]] . the <code></code> of the <code>[://gitlab//]</code> //.
https:// phabricator. wikimedia. org/ T287279</ ref>
//. . //
There are efforts to move all of the installation and configuration to puppet: [[ phab:T287279#7237735| T287279#7237735]].
to all [[|]].
Future Gitlab Runner setup ([[phab:T286958|T286958]]) ===
This section contains the requirements and plan for a future Gitlab-Runner setup. The goal is to find a secure, scalable and easy to build and maintain setup for the GitLab Runner infrastructure.
the and .
==== Compute Resources ====
GitLab Runner can run on various platforms, such as Kubernetes, Docker, OpenShift or just Linux VMs. Furthermore a wide range of compute platforms can be leveraged, such as WMCS, Ganetti, bare metal hosts or public clouds. So this section tries to compare the different options and collect advantages and disadvantages. Privacy considerations can be found in the next section.
===== Elastic demand =====
==== Privacy considerations ====
===== Whether these can safely run on a third-party platform =====
==== Monitoring of performance and usage ====
Gitlab-Runner export Prometheus metrics. This metrics should give insights in performance and usage. See [https://docs.gitlab.com/runner/monitoring/ Monitoring Gitlab Runner] documentation.
However the Gitlab Runner exporter does not support authorization or https. So depending on where the Runners are hosted, a https proxy with authorization is required.
GitLab Runner is an application that works with GitLab CI/CD to run jobs in a pipeline. For more information see the official GitLab Runner documentation.
GitLab Runner types
GitLab offers different types of CI Runners. Shared GitLab Runners are general purpos CI workers. This Runners execute jobs for a wide range of projects inside the
/repos group in GitLab. If access to this kind of Runners is needed, consider moving to the
/repos group and make yourself familiar with the details under Shared GitLab Runners.
Trusted GitLab Runners offer a platform for CI jobs with additional security needs (like building production artifacts). This Runners live inside WMF infrastructure and access to this Runners is gated and restricted. Access has to be requested on project basis, so please take a look on Trusted GitLab Runners on how to get access.
It is planned to add CI support for all projects using Cloud Runners. This Runners are in design phase and access to this Runners will be announced.
Evaluation and Design
Evaluation sub-pages on the right menu offer more insights into the design and security considerations.