60 lines
1.9 KiB
Markdown
60 lines
1.9 KiB
Markdown
# Gitea Actions Runner Configuration for j3270
|
|
|
|
This repository includes Gitea Actions workflows in `.gitea/workflows/build.yaml` to automatically:
|
|
1. Compile and run unit tests.
|
|
2. Build the standalone `j3270.jar` executable via `build_all.sh`.
|
|
3. Upload `j3270.jar` as a downloadable artifact.
|
|
4. Report test results and diagnostics.
|
|
|
|
---
|
|
|
|
## 1. Setting up `act_runner` (Gitea Actions Runner)
|
|
|
|
To run CI workflows on your Gitea instance:
|
|
|
|
### Step 1: Download `act_runner`
|
|
Download the `act_runner` binary for your platform from the [Gitea act_runner releases](https://gitea.com/gitea/act_runner/releases).
|
|
|
|
### Step 2: Register the Runner
|
|
Obtain a runner registration token from **Repository Settings -> Actions -> Runners** or **Admin -> Actions -> Runners**, then register:
|
|
|
|
```bash
|
|
./act_runner register \
|
|
--instance https://your-gitea-instance.com \
|
|
--token <YOUR_REGISTRATION_TOKEN> \
|
|
--name "j3270-runner" \
|
|
--labels "ubuntu-latest:docker://node:18-bullseye,ubuntu-22.04:docker://node:18-bullseye"
|
|
```
|
|
|
|
### Step 3: Run the Runner Daemon
|
|
```bash
|
|
./act_runner daemon
|
|
```
|
|
|
|
Or using Docker Compose:
|
|
```yaml
|
|
version: '3.8'
|
|
services:
|
|
runner:
|
|
image: gitea/act_runner:latest
|
|
restart: always
|
|
environment:
|
|
- GITEA_INSTANCE_URL=https://your-gitea-instance.com
|
|
- GITEA_RUNNER_REGISTRATION_TOKEN=<YOUR_REGISTRATION_TOKEN>
|
|
- GITEA_RUNNER_NAME=j3270-runner
|
|
- GITEA_RUNNER_LABELS=ubuntu-latest:docker://node:18-bullseye
|
|
volumes:
|
|
- /var/run/docker.sock:/var/run/docker.sock
|
|
- ./data:/data
|
|
```
|
|
|
|
---
|
|
|
|
## 2. CI/CD Workflow Summary
|
|
|
|
- **Trigger**: Pushes to `master`/`main`/`develop`, pull requests, and manual triggers via `workflow_dispatch`.
|
|
- **Artifacts**:
|
|
- `j3270-executable-jar`: Ready-to-run desktop terminal emulator jar (`java -jar j3270.jar`).
|
|
- `test-reports`: Full JUnit test reports and XML/HTML summaries.
|
|
- **Reporting**: On failure, automated diagnostic reports are generated and attached to the run summary.
|