act_runner工程镜像
Go to file
sillyguodong 0d71463662 Inject version when building and report version to Gitea via log and header (#43)
close #42
1. Inject runner version when `make build`
After building, executing command line: `./act_runner -v` or `./act_runner --version`, the version of runner is printed.
![image](/attachments/e25efbd3-79b3-49a5-b93f-42646d42c707)

2. In `Actions` UI:
![image](/attachments/36c57470-2a1d-4796-9eb0-de3988ab88e1)

3. Set request header in http client interceptor.

Co-authored-by: sillyguodong <gedong_1994@163.com>
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/43
Reviewed-by: delvh <dev.lh@web.de>
Reviewed-by: Jason Song <i@wolfogre.com>
Co-authored-by: sillyguodong <sillyguodong@noreply.gitea.io>
Co-committed-by: sillyguodong <sillyguodong@noreply.gitea.io>
2023-03-13 18:57:35 +08:00
.gitea/workflows run nightly on ubuntu runner 2023-03-01 12:32:00 +08:00
artifactcache fix lint error (#30) 2023-03-01 06:40:20 +08:00
client Inject version when building and report version to Gitea via log and header (#43) 2023-03-13 18:57:35 +08:00
cmd Inject version when building and report version to Gitea via log and header (#43) 2023-03-13 18:57:35 +08:00
config Add runner name to log (#37) 2023-03-06 18:42:07 +08:00
core Inject version when building and report version to Gitea via log and header (#43) 2023-03-13 18:57:35 +08:00
engine Add copyright header and gitea-vet (#29) 2023-02-28 18:44:46 +08:00
poller Add copyright header and gitea-vet (#29) 2023-02-28 18:44:46 +08:00
register Add copyright header and gitea-vet (#29) 2023-02-28 18:44:46 +08:00
runtime Inject version when building and report version to Gitea via log and header (#43) 2023-03-13 18:57:35 +08:00
.gitignore Add runner name to log (#37) 2023-03-06 18:42:07 +08:00
.golangci.yml chore: add .golangci config 2022-11-24 15:36:28 +08:00
.goreleaser.yaml Inject version when building and report version to Gitea via log and header (#43) 2023-03-13 18:57:35 +08:00
LICENSE Add license 2022-11-24 15:36:16 +08:00
Makefile Inject version when building and report version to Gitea via log and header (#43) 2023-03-13 18:57:35 +08:00
README.md feat: don't require docker (#16) 2023-01-27 20:42:02 +08:00
build.go Support cache (#25) 2023-02-28 23:39:30 +08:00
go.mod Support cache (#25) 2023-02-28 23:39:30 +08:00
go.sum Support cache (#25) 2023-02-28 23:39:30 +08:00
main.go Add copyright header and gitea-vet (#29) 2023-02-28 18:44:46 +08:00

README.md

act runner

Act runner is a runner for Gitea based on act.

Prerequisites

Docker Engine Community version is required. To install Docker CE, follow the official install instructions.

Quickstart

Build

make build

Register

./act_runner register

And you will be asked to input:

  1. Gitea instance URL, like http://192.168.8.8:3000/. You should use your gitea instance ROOT_URL as the instance argument and you should not use localhost or 127.0.0.1 as instance IP;
  2. Runner token, you can get it from http://192.168.8.8:3000/admin/runners;
  3. Runner name, you can just leave it blank;
  4. Runner labels, you can just leave it blank.

The process looks like:

INFO Registering runner, arch=amd64, os=darwin, version=0.1.5.
WARN Runner in user-mode.
INFO Enter the Gitea instance URL (for example, https://gitea.com/):
http://192.168.8.8:3000/
INFO Enter the runner token:
fe884e8027dc292970d4e0303fe82b14xxxxxxxx
INFO Enter the runner name (if set empty, use hostname:Test.local ):

INFO Enter the runner labels, leave blank to use the default labels (comma-separated, for example, self-hosted,ubuntu-20.04:docker://node:16-bullseye,ubuntu-18.04:docker://node:16-buster):

INFO Registering runner, name=Test.local, instance=http://192.168.8.8:3000/, labels=[ubuntu-latest:docker://node:16-bullseye ubuntu-22.04:docker://node:16-bullseye ubuntu-20.04:docker://node:16-bullseye ubuntu-18.04:docker://node:16-buster].
DEBU Successfully pinged the Gitea instance server
INFO Runner registered successfully.

You can also register with command line arguments.

./act_runner register --instance http://192.168.8.8:3000 --token <my_runner_token> --no-interactive

If the registry succeed, it will run immediately. Next time, you could run the runner directly.

Run

./act_runner daemon