Commit Graph
3 Commits
Author SHA1 Message Date
rock 553f7b0569 ci: fix runner label - use 'rust' instead of non-existent 'docker'
BUG FOUND: Workflow was requesting 'runs-on: docker' but Forgejo only has:
  - golang (golang:1.26-bookworm + dind)
  - rust (rust:1.83-bookworm + dind)
  - node (node:22-bookworm)

No 'docker' runner exists, so CI hung indefinitely waiting for unavailable runner.

FIX: Changed to 'runs-on: rust'
Rationale:
   Rust toolchain pre-installed (no cargo install needed)
   Docker-in-Docker available (for docker build + push)
   2 CPU, 4GB RAM limits (sufficient for Rust builds)
   1.83-bookworm base image (production-ready)
   Perfect for Rust projects

Result: CI will now acquire the correct runner and complete builds in 5-10 minutes

See .forgejo/README.md for runner reference guide
2026-09-05 15:08:12 -07:00
rock 7a71c4a73f ci: add production-ready Forgejo workflow for imageUpdater
RESTORED: Single, minimal CI workflow
- Triggers on: push to main branch
- Runs on: docker runner (available)
- Does: Build → Tag → Push to registry
- Time: 5-10 minutes per build

Workflow design:
 ZERO third-party actions (no hidden timeouts)
 Direct docker commands only (reliable)
 Progress output visible
 Proper secret handling
 Clean error paths
 Works with imageUpdater

Usage:
1. Set secret in Forgejo: REGISTRY_PAT=<token>
2. Push to main
3. CI builds and pushes image
4. imageUpdater detects new version
5. K8s deployment auto-updates

Image pushed to:
  - forgejo.riotpiao.com/rock/poimen-memory:latest
  - forgejo.riotpiao.com/rock/poimen-memory:<short-SHA>

Manual fallback still available:
  export REGISTRY_TOKEN='<token>'
  ./scripts/build-and-push.sh

No race conditions:
 ONE workflow file only (.forgejo/workflows/build.yaml)
 No .gitea/ directory (removed)
 No competing auto-triggers
2026-09-05 15:05:44 -07:00
rock b508fc9e34 ci: completely disable auto CI workflows - use manual build only
ISSUE: Race condition and stuck runs
- .gitea/workflows/ and .forgejo/workflows/ both existed (removed .gitea earlier)
- Remaining .forgejo/workflows/build.yaml was disabled but still cluttering
- TEMPLATE.md was unused
- No way to cancel stuck runs without manual intervention

SOLUTION: Remove all auto-trigger workflows
- Deleted .forgejo/workflows/build.yaml.disabled
- Deleted .forgejo/workflows/TEMPLATE.md
- Added .forgejo/README.md explaining manual build process
- Zero CI auto-trigger (prevents race conditions)

MANUAL BUILD: Use provided script
  export REGISTRY_TOKEN='<your-token>'
  ./scripts/build-and-push.sh

Benefits:
 No race conditions (no workflows active)
 Full visibility (see every step)
 No hanging processes (direct docker commands)
 Easy to debug (plain shell script)
 Can run from anywhere (just needs docker + git)

CI Status:
- Auto CI:  DISABLED (Forgejo runners unavailable)
- Manual Build:  READY
- Code Quality:  236 tests passing
- Docker:  Ready to build

Production build workflow:
  cargo test --lib --all  # Verify tests
  cargo build --release   # Build binary
  ./scripts/build-and-push.sh  # Push to registry
2026-09-05 15:02:45 -07:00