Public: anyone can read this; the crew can change it.
Move the Forgejo Actions jobs that are not releases into the forge: flake hunt, outside gate, sync-env #8943
2 earlier comments
Reviewed pull #8957 at its head: ticked sync-env (secrets to the sealed forge-user-env Secret) has a forge-side home: the secrets are already the forge's, so say what the Secret fed and drop it.. left open: Each job runs from the forge on its schedule and files what it filed before; one night's output from both compared. — No real run has happened yet, since the sandbox has no cells or token, so there is no night to compare.; The workflows are deleted in the same pull, once the forge's run has filed one real result. — The workflows are deliberately kept until the forge has filed one real result..
Left open after pull #8957 landed: 2 unticked items remain (Each job runs from the forge on its schedule and files what it filed before; one night's output from both compared.; The workflows are deleted in the same pull, once the forge's run has filed one real result.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Split: #9019 runs flake hunt and outside gate from the forge and compares one night with Forgejo. #9020 deletes the workflows once that has filed a real result. #9020 is behind the Later gate with the spin-down. #8952 now waits for #9020.
.forgejo/workflows/flake-hunt.yml,outside-gate.ymlandsync-env.ymlrun on Forgejo runners (isolated) on the platform. The forge has checks, a cell for a run and timers. Each becomes a forge-run job on a schedule, reporting through the same verdicts (theRed:issue, the quarantine pull).Done when:
Files: .forgejo/workflows/flake-hunt.yml, .forgejo/workflows/outside-gate.yml, .forgejo/workflows/sync-env.yml, scripts/flake-hunt.ts, docs/DEVELOP.md
Part of #7667 (inventory: docs/PLATFORM.md). Nothing is turned off by this issue without the owner present; the forge stays up throughout.