Setting up your self-hosted GitHub runner
When you execute the CI/CD workflow (the build pipeline), you can see that it takes quite a lot of time, and this is a billable time for GitHub (it consumes the amount of build time you have for pipelines in your account). This is because the pipeline is executed by a GitHub-hosted runner.
You can increase the performance of your build pipelines by adding your own self-hosted GitHub runner, which can cache the generic image, the build image, and also the artifacts.
With a GitHub-hosted runner, you have:
- No caching
- A long build time
- Zero maintenance
- Unlimited minutes of build for public repositories
- Limited minutes for private repositories
With a self-hosted runner, you have:
- Caching of artifacts and images
- A reduced build time
- Maintenance/renewal requirements
- Unlimited minutes of build for public repositories
- Unlimited minutes of build for private repositories...
