leeworks-agents/gitea-mobile
5
0
Fork 0
Code Issues 42 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

chore: update CI workflow runs-on label to match act_runner registration after #161 deployment #170

New Issue
Open
opened 2026-03-30 14:24:15 +00:00 by AI-Manager · 4 comments
AI-Manager commented 2026-03-30 14:24:15 +00:00
Owner
Copy Link
Copy Source

Summary

The CI workflow at .gitea/workflows/build.yaml uses runs-on: ubuntu-latest. This label must match the runner tag registered when act_runner is deployed (tracked in #161).

After issue #161 is complete and act_runner is running in the cluster, the workflow needs to be updated with the correct runs-on label that matches the runner registration.

What to Do

  1. Confirm the runner label used during act_runner registration in feat: deploy Gitea Actions act_runner as a Kubernetes workload in the cluster (#161)
  2. Update .gitea/workflows/build.yaml: 
    jobs:
  test:
    runs-on: <actual-runner-label>   # e.g. "gitea-runner" or "self-hosted"
  build:
    runs-on: <actual-runner-label>
  3. Commit, push, and verify the workflow triggers successfully on a push to master
  4. Confirm CI passes: go vet ./..., go test -race ./..., and Docker build+push steps complete

Acceptance Criteria

  • runs-on label in both test and build jobs matches the registered act_runner label
  • A push to master triggers the workflow and it completes without queuing forever
  • CI test step passes
  • CI build step pushes a new image tag to gitea.leeworks.dev/0xwheatyz/gitea-mobile
  • Flux picks up the new image tag automatically

References

  • Depends on: #161 (deploy act_runner as K8s workload)
  • ROADMAP.md Phase 3.4 — CI workflow
  • Partially addressed by closed issue #95 (runner label fix for a different runner context)
## Summary The CI workflow at `.gitea/workflows/build.yaml` uses `runs-on: ubuntu-latest`. This label must match the runner tag registered when `act_runner` is deployed (tracked in #161). After issue #161 is complete and `act_runner` is running in the cluster, the workflow needs to be updated with the correct `runs-on` label that matches the runner registration. ## What to Do 1. Confirm the runner label used during `act_runner` registration in #161 2. Update `.gitea/workflows/build.yaml`: ```yaml jobs: test: runs-on: <actual-runner-label> # e.g. "gitea-runner" or "self-hosted" build: runs-on: <actual-runner-label> ``` 3. Commit, push, and verify the workflow triggers successfully on a push to `master` 4. Confirm CI passes: `go vet ./...`, `go test -race ./...`, and Docker build+push steps complete ## Acceptance Criteria - [ ] `runs-on` label in both `test` and `build` jobs matches the registered act_runner label - [ ] A push to `master` triggers the workflow and it completes without queuing forever - [ ] CI test step passes - [ ] CI build step pushes a new image tag to `gitea.leeworks.dev/0xwheatyz/gitea-mobile` - [ ] Flux picks up the new image tag automatically ## References - Depends on: #161 (deploy act_runner as K8s workload) - ROADMAP.md Phase 3.4 — CI workflow - Partially addressed by closed issue #95 (runner label fix for a different runner context)
AI-Manager added the P3agent-readysmallblocked labels 2026-03-30 14:24:15 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 15:03:01 +00:00
AI-Manager commented 2026-03-30 15:03:27 +00:00
Author
Owner
Copy Link
Copy Source

Triage Report (Repo Manager)

Status: Blocked — depends on #161 (act_runner deployment) which is labeled needs-human.

What needs to happen: Once the act_runner is deployed and registered, the runs-on: ubuntu-latest label in .gitea/workflows/build.yaml (lines 10, 25) needs to be updated to match the runner's registered label.

Assigned to: AI-Engineer. This is a simple one-line change in the CI workflow file once the runner label is known.

No action needed now — this remains blocked until #161 is resolved.

## Triage Report (Repo Manager) **Status**: Blocked — depends on #161 (act_runner deployment) which is labeled `needs-human`. **What needs to happen**: Once the act_runner is deployed and registered, the `runs-on: ubuntu-latest` label in `.gitea/workflows/build.yaml` (lines 10, 25) needs to be updated to match the runner's registered label. **Assigned to**: AI-Engineer. This is a simple one-line change in the CI workflow file once the runner label is known. **No action needed now** — this remains blocked until #161 is resolved.
AI-Manager commented 2026-03-31 01:07:36 +00:00
Author
Owner
Copy Link
Copy Source

Triage Analysis (2026-03-31)

Assessment: This issue may already be resolved.

The CI workflow (.gitea/workflows/build.yaml) uses runs-on: ubuntu-latest for both the test and build jobs. The act_runner in the Talos deployment manifest is configured with label ubuntu-latest:docker://node:20-bullseye.

These match. However, the Go test step needs a Go toolchain, and node:20-bullseye does not include Go. The actions/setup-go@v5 step should install it, but this depends on whether the act_runner environment supports GitHub Actions-compatible toolchain installation.

Potential issue: The build job runs docker build and docker login/push. Since the runner uses DinD, this should work. But the test job relies on actions/setup-go@v5 which may or may not work correctly in the act_runner node image.

Action: Verify after #161 is deployed. If CI fails, the label or base image may need updating (e.g., using a Go-based Docker image for the test job).

## Triage Analysis (2026-03-31) **Assessment**: This issue may already be resolved. The CI workflow (`.gitea/workflows/build.yaml`) uses `runs-on: ubuntu-latest` for both the `test` and `build` jobs. The act_runner in the Talos deployment manifest is configured with label `ubuntu-latest:docker://node:20-bullseye`. These match. However, the Go test step needs a Go toolchain, and `node:20-bullseye` does not include Go. The `actions/setup-go@v5` step should install it, but this depends on whether the act_runner environment supports GitHub Actions-compatible toolchain installation. **Potential issue**: The `build` job runs `docker build` and `docker login/push`. Since the runner uses DinD, this should work. But the `test` job relies on `actions/setup-go@v5` which may or may not work correctly in the act_runner node image. **Action**: Verify after #161 is deployed. If CI fails, the label or base image may need updating (e.g., using a Go-based Docker image for the test job).
AI-Manager commented 2026-04-19 20:04:19 +00:00
Author
Owner
Copy Link
Copy Source

Repo Manager (2026-04-19): Blocked on #161 (act_runner). Runner manifests exist in Talos repo but no runners are registered. The runs-on label cannot be verified until a runner is operational.

Repo Manager (2026-04-19): Blocked on #161 (act_runner). Runner manifests exist in Talos repo but no runners are registered. The runs-on label cannot be verified until a runner is operational.
AI-Manager commented 2026-04-19 23:06:40 +00:00
Author
Owner
Copy Link
Copy Source

Triage (2026-04-19)

Status: Blocked on #161 (act_runner deployment). Once the runner is deployed, the runs-on label in .gitea/workflows/build.yaml may need updating to match the runner registration. Currently uses ubuntu-latest. This is a trivial one-line change but cannot be validated until the runner exists.

## Triage (2026-04-19) **Status:** Blocked on #161 (act_runner deployment). Once the runner is deployed, the `runs-on` label in `.gitea/workflows/build.yaml` may need updating to match the runner registration. Currently uses `ubuntu-latest`. This is a trivial one-line change but cannot be validated until the runner exists.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
blocked
Blocked by another issue
 large
medium
needs-human
small
No Label P3 agent-ready blocked small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/gitea-mobile#170
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?