Switch ZedWatch workflows to the dedicated runner #24

New issue

Open

opened 2026-08-23 17:07:58 +00:00 by stanta · 0 comments

stanta commented

2026-08-23 17:07:58 +00:00

Owner

Outcome

Move the intended ZedWatch Rust and image builds to dedicated VM 112 and prove the build path.

Current state

The dedicated runner is registered with the rust-dedicated label. Workflow switching and representative build tests remain pending.

Work

Inventory ZedWatch workflows that should use the runner.
Apply the dedicated runner label.
Confirm caches and artifact paths.
Run Rust and container-image builds.
Confirm the runner cannot reach blocked homelab networks.
Keep trusted homelab workflows on the global runner.

Validation

Representative ZedWatch builds pass on VM 112.
The global runner no longer receives those jobs.
Network-isolation probes still pass.

References

iac/DEDICATED-SERVER.md
iac/ansible/inventory.dedicated.yml
iac/ansible/roles/forgejo_runner/

## Outcome Move the intended ZedWatch Rust and image builds to dedicated VM 112 and prove the build path. ## Current state The dedicated runner is registered with the `rust-dedicated` label. Workflow switching and representative build tests remain pending. ## Work - [ ] Inventory ZedWatch workflows that should use the runner. - [ ] Apply the dedicated runner label. - [ ] Confirm caches and artifact paths. - [ ] Run Rust and container-image builds. - [ ] Confirm the runner cannot reach blocked homelab networks. - [ ] Keep trusted homelab workflows on the global runner. ## Validation - [ ] Representative ZedWatch builds pass on VM 112. - [ ] The global runner no longer receives those jobs. - [ ] Network-isolation probes still pass. ## References - `iac/DEDICATED-SERVER.md` - `iac/ansible/inventory.dedicated.yml` - `iac/ansible/roles/forgejo_runner/`

stanta added the

labels

2026-08-23 17:07:58 +00:00