https://github.com/abelsiqueira/self-hosted-runners

Recipe to install and configure a GitHub action runner using Ansible

https://github.com/abelsiqueira/self-hosted-runners

Repository

Recipe to install and configure a GitHub action runner using Ansible

https://github.com/abelsiqueira/self-hosted-runners/blob/master/

# Self-hosted runners

| Five recommendations for fair software from [fair-software.nl](https://fair-software.nl) | Badges |
| --- | --- |
| 1. Code repository | [![GitHub badge](https://img.shields.io/badge/github-repo-000.svg?logo=github&labelColor=gray&color=blue)](https://github.com/ci-for-science/self-hosted-runners/) |
| 2. License | [![License badge](https://img.shields.io/github/license/ci-for-science/self-hosted-runners)](https://github.com/ci-for-science/self-hosted-runners/) |
| 3. Community registry | [![Ansible Galaxy badge](https://img.shields.io/badge/galaxy-fixme.fixme-660198.svg)](https://galaxy.ansible.com/fixme/fixme) [![Research Software Directory](https://img.shields.io/badge/rsd-self--hosted--runners-00a3e3.svg)](https://www.research-software.nl/software/self-hosted-runners) |
| 4. Enable citation | [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.3904265.svg)](https://doi.org/10.5281/zenodo.3904265) |
| 5. Checklist | N/A |
| **Other best practices** | |
| Markdown Link Checker| [![Check Markdown links](https://github.com/ci-for-research/self-hosted-runners/workflows/Check%20Markdown%20links/badge.svg)](https://github.com/ci-for-research/self-hosted-runners/actions?query=workflow%3A%22Check+Markdown+links%22) |

## How to set up GitHub Action runners on self-hosted infrastructure

This repository explains how to set up a server for running continuous integration tests on other hardware than what
GitHub provides. This can be useful when the code you want to test has special requirements, for example if

- it needs a GPU to run ([CUDA installation with ansible instructions](/install-cuda/README.md))
- it needs multiple nodes
- testing requires data that needs to stay on-premises for privacy reasons or legal reasons
- testing requires data that is too big to move
- testing requires specific software

This guide distinguishes between the _client_ and the _server_; the client is your own machine; the server is whichever
machine runs the tests. For either side, we'll explain what configuration needs to be done. For people who just want to
try out the instructions but don't have access to remote hardware, we included a few alternatives for running the server
locally as well, through the use of virtualization (with VirtualBox) and containerization (with Docker).

For the client, we included instructions for Linux Ubuntu, Mac, and Windows; the server-side instructions all assume
Linux Ubuntu.

| Status | Client OS | Server hardware | Runner |
| --- | --- | --- | --- |
| :heavy_check_mark: Completed | Linux Ubuntu | local machine via Docker           | [link](/ubuntu-docker/README.md)          |
| :heavy_check_mark: Completed | Linux Ubuntu | local machine via Singularity      | [link](/ubuntu-singularity/README.md)     |
| :heavy_check_mark: Completed | Linux Ubuntu | local machine via Vagrant          | [link](/ubuntu-vagrant/README.md)         |
| :heavy_check_mark: Completed | Linux Ubuntu | local machine via VirtualBox       | [link](/ubuntu-virtualbox/README.md)      |
| :heavy_check_mark: Completed | Linux Ubuntu | remote machine at [SURF HPC Cloud] | [link](/ubuntu-surf-hpc-cloud/README.md)  |
| :hourglass_flowing_sand: WIP | Mac          | local machine via Docker           | -                                         |
| :hourglass_flowing_sand: WIP | Mac          | local machine via Vagrant          | -                                         |
| :hourglass_flowing_sand: WIP | Mac          | local machine via VirtualBox       | -                                         |
| :hourglass_flowing_sand: WIP | Mac          | remote machine at [SURF HPC Cloud] | -                                         |
| :hourglass_flowing_sand: WIP | Windows      | local machine via Docker           | -                                         |
| :heavy_check_mark: Completed | Windows      | local machine via Vagrant          | [link](windows-vagrant/README.md)         |
| :hourglass_flowing_sand: WIP | Windows      | local machine via VirtualBox       | -                                         |
| :heavy_check_mark: Completed | Windows      | remote machine at [SURF HPC Cloud] | [link](/windows-surf-hpc-cloud/README.md) |

## Security

**A warning from GitHub for self-hosted runners in combination with public repositories is shown
[here](https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories).
Please take this seriously. It basically means that the combination of a self-hosted runner and a public GitHub
repository is unsafe. However, there was a [recent discussion](https://github.com/actions/runner/issues/494) indicating
that GitHub may add features to make this combination safe in the near future.**

[SURF HPC Cloud]: https://userinfo.surfsara.nl/systems/hpc-cloud

## Documentation for developers


If you want to check if the links in your markdown work, install markdown-link-check

```shell
npm install
```

then run

```shell
find . -name '*.md' -not -path './node_modules/*' -exec markdown-link-check '{}' --config .mlc-config.json ';'
```

Owner

GitHub Events