STACKITGit/end-to-end
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request 'chore(readme): explain how to use a locally built runner' (#514) from earl-warren/end-to-end:wip-local-runner into main

Browse source 
Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/514
This commit is contained in:
earl-warren 2025-01-28 16:57:12 +00:00
commit 16dba44733
No known key found for this signature in database
GPG key ID: F128CBE6AB3A7201
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -48,6 +48,13 @@ cd end-to-end
## Running from locally built binary
Before injecting a manually built binary, make sure a simple test was
run so that the directories are populated.
### Forgejo
From a checkout of https://codeberg.org/forgejo/forgejo/
```sh
make TAGS='bindata sqlite sqlite_unlock_notify' generate forgejo
cp -a forgejo /srv/forgejo-binaries/forgejo-10.0
@ -55,6 +62,15 @@ cp -a forgejo /srv/forgejo-binaries/forgejo-10.0
It will be used whenever the version `10.0` is specified in a test.
### Forgejo runner
From a checkout of https://code.forgejo.org/forgejo/runner
```sh
make --always-make forgejo-runner
cp forgejo-runner /tmp/forgejo-end-to-end/forgejo-runner
```
## Running actions locally
To run and debug workflows from `actions/example-*`, from the root of