earl-warren
781606388c
All checks were successful
checks / build and test (push) Successful in 1m13s
checks / runner exec tests (push) Successful in 1m17s
/ example-docker-compose (push) Successful in 3m28s
Build release / release (push) Has been skipped
pubish / publish (push) Has been skipped
Integration tests for the release process / release-simulation (push) Successful in 6m59s
Reviewed-on: #167 Reviewed-by: twenty-panda <twenty-panda@noreply.code.forgejo.org> Reviewed-by: Michael Kriese <michael.kriese@gmx.de> |
||
|---|---|---|
| .forgejo | ||
| examples | ||
| internal | ||
| scripts | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| build.go | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| README.md | ||
| RELEASE-NOTES.md | ||
Forgejo Runner
WARNING: this is alpha release quality code and should not be considered secure enough to deploy in production.
A daemon that connects to a Forgejo instance and runs jobs for continous integration. The installation and usage instructions are part of the Forgejo documentation.
Hacking
The Forgejo runner depends on a fork of ACT and is a dependency of the setup-forgejo action. See the full dependency graph for a global view.
Local debug
The repositories are checked out in the same directory:
- runner: Forgejo runner
- act: ACT
- setup-forgejo: setup-forgejo
Install dependencies
The dependencies are installed manually or with:
setup-forgejo/forgejo-dependencies.sh
Build the Forgejo runner with the local ACT
The Forgejo runner is rebuilt with the ACT directory by changing the runner/go.mod file to:
replace github.com/nektos/act => ../act
Running:
cd runner ; go mod tidy
Building:
cd runner ; rm -f forgejo-runner ; make forgejo-runner
Launch Forgejo and the runner
A Forgejo instance is launched with:
cd setup-forgejo
./forgejo.sh setup
firefox $(cat forgejo-url)
The user is root with password admin1234. The runner is registered with:
cd setup-forgejo
docker exec --user 1000 forgejo forgejo actions generate-runner-token > forgejo-runner-token
../runner/forgejo-runner register --no-interactive --instance "$(cat forgejo-url)" --name runner --token $(cat forgejo-runner-token) --labels docker:docker://node:16-bullseye,self-hosted:host://-self-hosted,lxc:lxc://debian:bullseye
And launched with:
cd setup-forgejo ; ../runner/forgejo-runner --config runner-config.yml daemon
Note that the runner-config.yml is required in that particular case
to configure the network in bridge mode, otherwise the runner will
create a network that cannot reach the forgejo instance.
Try a sample workflow
From the Forgejo web interface, create a repository and add the
following to .forgejo/workflows/try.yaml. It will launch the job and
the result can be observed from the actions tab.
on: [push]
jobs:
ls:
runs-on: docker
steps:
- uses: actions/checkout@v3
- run: |
ls ${{ github.workspace }}