You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
This page is documentation of the github actions runner we plan to use
Possible setup #1 - GitHub enterprise
Possible setup #2 - Self hosted runner
I made a self-hosted runner that runs in a container on s3df on a repository named BuildSystem.
But also communicates with github, and posts build results there under the 'Action' tab.
- Here is setup
- And then run, and manually trigger the workflow using Github CLI (I installed github CLI on my goenv)
Result on github repo 'Actions'
To think about: Should we use github CLI to be the base tool for our CLI? It seems to have features we need like triggering a workflow manually. But it also allows you to create your own commands. Maybe we can make a simplified wrapper around the CLI - And make only certain options visible to the end user?
Resources:
Provide runner as a Docker Image · Issue #367 · actions/runner (github.com)
Package actions-runner (github.com)
Adding self-hosted runners - GitHub Docs
If go this route:
- Add the self-hosted runner at the organization level
- (optional) configure the self-hosted runner as a service
Possible setup #3 - Self hosted runner with jobs in containers
Running jobs in a container - GitHub Docs