Skip to content

Make the arc-runners scale set CI-capable (docker-compose, browsers, container actions) + allow MendysRoboticsWP #250

Description

@izzywdev

Request (from izzywdev/MendysRobotics via delegate-to-fuzeinfra)

@claude — we tried to move MendysRobotics/MendysRoboticsWP CI onto the self-hosted mendysrobotics ARC scale set to escape GitHub-hosted runner-budget exhaustion. The runner picks up jobs (great), but it's a minimal k8s pod that can't run our CI gates, so we had to revert most jobs back to ubuntu-latest. Please upgrade the arc-runners image/template so consumer CI can run on it.

What failed on the ARC runner (real job logs)

  • gate-integration / gate-localup / Integration-Contract-Tests → no docker-compose: unknown shorthand flag: 'f' in -f (our jobs use docker compose -f docker-compose.consumer-test.yml up -d --wait).
  • gate-sast / gate-authzSemgrep produced no SARIF (Path does not exist: authz.sarif) — container-action / tooling gap.
  • build-test / docker-build / build-and-push → need docker build + buildx.
  • e2e-visual / prod-* / frontend-quality → need Playwright browsers (npx playwright install --with-deps).

Please add to the arc-runners runner image/scale-set (or document how consumers get them)

  1. docker + docker compose v2 (plugin) + buildx available in-runner (dind sidecar or mounted docker socket) so docker compose / docker build work.
  2. Ability to run container-based actions (Semgrep/Trivy/gitleaks) — i.e. the runner can docker run action containers.
  3. A path to install Playwright/Chromium (system deps for --with-deps), or a browsers-preinstalled variant.
  4. Baseline: git, curl, jq, node, python + setup-* action tool-cache writable (these mostly work today).

Cross-repo access

  1. ARC scale sets are registered per-repo. We want izzywdev/MendysRoboticsWP to run on the same mendysrobotics scale set (or its own). Please enable org/cross-repo access for it, or advise onboarding a mendysroboticswp scale set (WP has no arc-register today).

Also (re-raising the earlier request)

  1. Annotate namespaces mendys-prod and mendys-wp with fuzeinfra.io/owner-repo=izzywdev/MendysRobotics (via managedNamespaceMetadata) so the Grafana crit-log → grafana-crit-fix.yml autofix routes error-log alerts to our repo. (Separate delegate issue already filed; consolidating here for visibility.)

We own only deploy/** and can't operate the shared cluster — hence this delegation. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions