... | ... | @@ -14,10 +14,6 @@ CI as that will be the likely, long term replacement. |
|
|
[GitLab CI][GitLab CI splash] has [good documentation upstream][GitLab CI upstream]. This section
|
|
|
documents frequent questions we might get about the work.
|
|
|
|
|
|
[GitLab CI upstream]: https://docs.gitlab.com/ee/ci/
|
|
|
[GitLab CI splash]: https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/
|
|
|
[GitLab CI quickstart]: https://docs.gitlab.com/ee/ci/quick_start/README.html
|
|
|
|
|
|
<!-- simple, brainless step-by-step instructions requiring little or -->
|
|
|
<!-- no technical background -->
|
|
|
|
... | ... | @@ -37,7 +33,6 @@ be available to all projects. So your main task here is basically to |
|
|
There might be too many jobs in the queue. You can monitor the queue
|
|
|
in our [Grafana dashboard](https://grafana.torproject.org/d/QrDJktiMz/gitlab-omnibus).
|
|
|
|
|
|
|
|
|
## Enabling/disabling runners
|
|
|
|
|
|
If a runner is misbehaving, it might be worth "pausing" it while we
|
... | ... | @@ -565,9 +560,9 @@ TPA's approbation required for the libvirt exception, see |
|
|
|
|
|
## Proposed Solution
|
|
|
|
|
|
The [original proposal][issue 40095] from @ahf when as follows:
|
|
|
The [original proposal][issue 40095] from @ahf was as follows:
|
|
|
|
|
|
> [...] Reserve two (ideally) "fast" Debian-based machines on TPO infrastructure to build the following:
|
|
|
> \[...\] Reserve two (ideally) "fast" Debian-based machines on TPO infrastructure to build the following:
|
|
|
>
|
|
|
> * Run Gitlab CI runners via KVM (initially with focus on Windows
|
|
|
> x86-64 and macOS x86-64). This will replace the need for Travis CI
|
... | ... | @@ -591,7 +586,7 @@ using [libvirt](https://libvirt.org/) (see [this example implementation](https:/ |
|
|
|
|
|
This is an excerpt from the [proposal sent to TPA][TPA-RFC-8]:
|
|
|
|
|
|
> [TPA would] build two (bare metal) machines (in the Cymru cluster)
|
|
|
> \[TPA would\] build two (bare metal) machines (in the Cymru cluster)
|
|
|
> to manage those runners. The machines would grant the GitLab runner
|
|
|
> (and also @ahf) access to the libvirt environment (through a role
|
|
|
> user).
|
... | ... | |