Files
tri-pi/.github/workflows/README.md
T
Krystie ef984d86db Add GitHub Actions auto-build pipeline
- Automatic ARM64 builds when new triangles_v5 releases detected
- Scheduled checks every 6 hours
- Manual dispatch for on-demand builds
- Creates GitHub releases with binaries
- Updates VERSION tracking

Build process:
- Uses Docker ARM64 (QEMU) for native builds
- Builds BerkeleyDB 4.8 from source
- Compiles trianglesd with full Tor integration
- Generates release packages with checksums
- Auto-commits and creates releases
2026-04-01 04:09:37 -07:00

52 lines
1.3 KiB
Markdown

# TRI-PI GitHub Actions
## Automated Build Pipeline
This repository uses GitHub Actions to automatically rebuild TRI-PI whenever a new version of triangles_v5 is released.
### Workflows
#### `build-arm64.yml` - Automatic ARM64 Builder
**Triggers:**
1. **Manual dispatch** - Run builds on demand via GitHub UI
2. **Scheduled checks** - Every 6 hours, checks for new triangles_v5 releases
3. **Auto-build** - When a new version is detected, builds automatically
**What it does:**
1. Checks for new triangles_v5 releases
2. Builds trianglesd from source in ARM64 Docker container
3. Creates release package (tar.gz)
4. Updates VERSION file and documentation
5. Commits and pushes to main branch
6. Creates GitHub Release with binaries
**Build environment:**
- Ubuntu 24.04 ARM64 (via QEMU emulation)
- BerkeleyDB 4.8 (built from source)
- Boost 1.83, OpenSSL 3.0
- Full Tor integration
### Manual Trigger
To manually build a specific version:
1. Go to **Actions** tab
2. Select **Build TRI-PI ARM64** workflow
3. Click **Run workflow**
4. Enter version tag (e.g., `v5.4.5`)
5. Click **Run workflow**
### Automatic Updates
The workflow runs every 6 hours to check for new releases. When detected:
- Builds automatically
- Creates release
- Updates repo
No manual intervention needed!
### Version Tracking
Current version stored in `VERSION` file at repo root.