... | ... | @@ -427,12 +427,15 @@ We currently use the following tags: |
|
|
runners, `KVM` runners are possibly more powerful and can, for
|
|
|
example, run Docker-inside-Docker (DinD)
|
|
|
* **memory** size: `64GB`, `32GB`, `4GB`, etc.
|
|
|
* `privileged`: those containers have actual root access and should
|
|
|
explicitly be able to run `DinD`
|
|
|
* `interactive web terminal`: supports [interactively debugging
|
|
|
jobs](https://docs.gitlab.com/ee/ci/interactive_web_terminal/)
|
|
|
* `TPA`: runners managed by the sysadmin team
|
|
|
* `fdroid`: provided as a courtesy by the [F-Droid project](https://f-droid.org/)
|
|
|
* **hosting** provider:
|
|
|
* `TPA`: runners managed by the sysadmin team
|
|
|
* `fdroid`: provided as a courtesy by the [F-Droid project](https://f-droid.org/)
|
|
|
* `OSUOSL`: runners provided by the [OSUOSL](https://osuosl.org/)
|
|
|
* **features**:
|
|
|
* `privileged`: those containers have actual root access and should
|
|
|
explicitly be able to run `DinD`
|
|
|
* `interactive web terminal`: supports [interactively debugging
|
|
|
jobs](https://docs.gitlab.com/ee/ci/interactive_web_terminal/)
|
|
|
|
|
|
Use tags in your configuration only if your job can be fulfilled by
|
|
|
only some of those runners. For example, only specify a memory tag if
|
... | ... | |