Comment Comment by paulddraper GitHub Actions runners are hard to self-host.The runner configuration and registration process is unnecessarily byzantine. [1]They can't cancel jobs cleanly. [2]There are consistency problems everywhere. [3]Their own documentations describes horrible things unless you use runners in JIT mode. Though JIT runners are not always removed after exit.If there is a worse self-hosted CI runner, I haven't yet met it.[1] https://docs.github.com/en/actions/how-tos/manage-runners/se...[2] https://github.com/orgs/community/discussions/26311[3] https://github.com/orgs/community/discussions/62365 parent paulddraper 10 months ago
The runner configuration and registration process is unnecessarily byzantine. [1]
They can't cancel jobs cleanly. [2]
There are consistency problems everywhere. [3]
Their own documentations describes horrible things unless you use runners in JIT mode. Though JIT runners are not always removed after exit.
If there is a worse self-hosted CI runner, I haven't yet met it.
[1] https://docs.github.com/en/actions/how-tos/manage-runners/se...
[2] https://github.com/orgs/community/discussions/26311
[3] https://github.com/orgs/community/discussions/62365