|
| 1 | +# External CI Runners |
| 2 | + |
| 3 | +The Rust Project mainly runs Continuous Integration (CI) in GitHub Actions. |
| 4 | +When GitHub Actions does not natively support a target, we use |
| 5 | +[self-hosted runners](https://docs.github.com/en/actions/concepts/runners/self-hosted-runners). |
| 6 | + |
| 7 | +## Configured external CI runners |
| 8 | + |
| 9 | +This section lists the external CI runners that are configured to run in the CI of the Rust Project. |
| 10 | + |
| 11 | +Here is an explanation of the fields in the list below: |
| 12 | + |
| 13 | +- `max concurrency`: The available number of runners of this type. |
| 14 | + This determines the maximum number of GitHub Actions jobs that can run on the runner. |
| 15 | + The concurrency is shared among repositories. If all runners are busy, GitHub Actions will queue |
| 16 | + the jobs until a runner is available. |
| 17 | +- `repositories`: The repositories that are enabled to use the runner. To add your repository to the |
| 18 | + list, please open a PR to this file. |
| 19 | + Make sure the workflow you want to run the runner on passes [`zizmor`](https://zizmor.sh/). |
| 20 | +- `contact`: The contact information of the person(s) responsible for maintaining the runner. |
| 21 | + The recommended way to contact them is via Zulip, by opening a new topic in the |
| 22 | + [#t-infra](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra) channel and mentioning |
| 23 | + the contact person(s). |
| 24 | + |
| 25 | +### `powerpc64-unknown-linux-musl` |
| 26 | + |
| 27 | +- max concurrency: 4 |
| 28 | +- repositories: |
| 29 | + - [`compiler-builtins`](https://github.com/rust-lang/compiler-builtins) |
| 30 | + - [`libc`](https://github.com/rust-lang/libc) |
| 31 | +- [example workflow](https://github.com/rust-lang/compiler-builtins/pull/1219) |
| 32 | +- contact: |
| 33 | + - Zulip: [Aelin](https://rust-lang.zulipchat.com/#user/338253) |
| 34 | + - Email: `aelin@postmarketos.org` (faster response) |
0 commit comments