GitHub runner
- Canonical IS DevOps
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 308 | 11 Dec 2024 | |
| latest/stable | 302 | 02 Dec 2024 | |
| latest/stable | 1 | 09 Feb 2022 | |
| latest/beta | 317 | 11 Dec 2024 | |
| latest/beta | 310 | 28 Nov 2024 | |
| latest/edge | 322 | 20 Dec 2024 | |
| latest/edge | 310 | 28 Nov 2024 | |
| latest/edge | 4 | 26 Apr 2022 | |
| local-lxd/stable | 306 | 17 Dec 2024 | |
| local-lxd/edge | 306 | 27 Nov 2024 | |
| 1/stable | 177 | 05 Jun 2024 | |
| 1/edge | 177 | 05 Jun 2024 |
juju deploy github-runner
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
22.04
20.04
External Access
The GitHub Runner Charm itself requires access to the
- GitHub API (e.g. to register and remove runners).
- GitHub website (e.g. to download the runner binary or other applications like yq)
- Ubuntu package repositories (e.g. to install packages)
- Snap store (e.g. to install LXD or aproxy)
- Ubuntu Cloud Images (for the image used by a runner)
- npm registry (e.g. to download and install specific packages)
In addition, access is required depending on the requirements of the workloads that the runners will be running (as they will be running on the same machine as the charm).
More details on network configuration can be found in the charm architecture documentation.