actions/actions-runner-controller
1
0
Fork 0
mirror of https://github.com/actions/actions-runner-controller.git synced 2025-12-14 13:46:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add acceptance test (#168)

Browse Source 
To ease verifying the controller to work before submitting/merging PRs and releasing a new version of the controller.
This commit is contained in:
Yusuke Kuoka
2020-11-14 20:07:14 +09:00
committed by GitHub
parent 8ccf64080c
commit bbfe03f02b
6 changed files with 118 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@@ -446,6 +446,28 @@ Your base64'ed PAT token has a new line at the end, it needs to be created witho
* `echo -n $TOKEN | base64`
* Create the secret as described in the docs using the shell and documeneted flags
# Developing
If you'd like to modify the controller to fork or contribute, I'd suggest using the following snippet for running
the acceptance test:
```shell
NAME=$DOCKER_USER/actions-runner-controller VERSION=dev \
GITHUB_TOKEN=*** \
APP_ID=*** \
PRIVATE_KEY_FILE_PATH=path/to/pem/file \
INSTALLATION_ID=*** \
make docker-build docker-push acceptance
```
Please follow the instructions explained in [Using Personal Access Token](#using-personal-access-token) to obtain
`GITHUB_TOKEN`, and those in [Using GitHub App](#using-github-app) to obtain `APP_ID`, `INSTALLATION_ID`, and
`PRIAVTE_KEY_FILE_PATH`.
The test creates a one-off `kind` cluster, deploys `cert-manager` and `actions-runner-controller`,
creates a `RunnerDeployment` custom resource for a public Git repository to confirm that the
controller is able to bring up a runner pod with the actions runner registration token installed.
# Alternatives
The following is a list of alternative solutions that may better fit you depending on your use-case: