... | ... | @@ -107,7 +107,7 @@ If you see a warning like: |
|
|
It's because the runner is taking up all the disk space. This is
|
|
|
usually containers, images, or caches from the runner. Those are
|
|
|
normally [purged regularly](#image-volume-and-container-storage-and-caching) but some extra load on the CI system
|
|
|
might use up too much space all of a sudden.
|
|
|
might use up too much space all of a sudden.
|
|
|
|
|
|
To diagnose this issue better, you can see the running containers
|
|
|
with:
|
... | ... | @@ -291,7 +291,7 @@ steps were taken on the machine: |
|
|
`roles::gitlab::ci::foreign`)
|
|
|
|
|
|
The `gitlab-ci-admin` role user and group have access to the
|
|
|
machine.
|
|
|
machine.
|
|
|
|
|
|
TODO: The remaining procedure still needs to be implemented and
|
|
|
documented, here, and eventually converted into a Puppet manifest, see
|
... | ... | @@ -586,7 +586,7 @@ preferred CI tool. |
|
|
|
|
|
Ever since the [GitLab migration](howto/gitlab), we have discussed the
|
|
|
possibility of replacing Jenkins with GitLab CI, or at least using
|
|
|
GitLab CI in some way.
|
|
|
GitLab CI in some way.
|
|
|
|
|
|
Tor currently utilizes a mixture of different CI systems to ensure
|
|
|
some form of quality assurance as part of the software development
|
... | ... | @@ -688,14 +688,14 @@ This is an excerpt from the [proposal sent to TPA][TPA-RFC-8]: |
|
|
> to manage those runners. The machines would grant the GitLab runner
|
|
|
> (and also @ahf) access to the libvirt environment (through a role
|
|
|
> user).
|
|
|
>
|
|
|
>
|
|
|
> ahf would be responsible for creating the base image and deploying the
|
|
|
> first machine, documenting every step of the way in the TPA wiki. The
|
|
|
> second machine would be built with Puppet, using those instructions,
|
|
|
> so that the first machine can be rebuilt or replaced. Once the second
|
|
|
> machine is built, the first machine should be destroyed and rebuilt,
|
|
|
> unless we are absolutely confident the machines are identical.
|
|
|
>
|
|
|
>
|
|
|
> [custom executor]: https://docs.gitlab.com/runner/executors/custom.html
|
|
|
|
|
|
## Cost
|
... | ... | @@ -753,7 +753,7 @@ idea would be to replace the "SSH + role user" approach we currently |
|
|
use for service with GitLab CI.
|
|
|
|
|
|
As explained in the [goals](#goals) section above, this is currently out of
|
|
|
scope, but could be considered instead of Docker for runners.
|
|
|
scope, but could be considered instead of Docker for runners.
|
|
|
|
|
|
### Jenkins
|
|
|
|
... | ... | |