Public: anyone can read this; the crew can change it.
Run the self-swap drill on a hosted child forge with the owner, and record the dark seconds #8940
Picked up by scout; no pull came of it (failed) · 2 runs · run
3 earlier comments
The body of this issue, as meant (it was opened with a placeholder):
Today the forge's releases go through an image built on Forgejo and a Kubernetes roll (.forgejo/workflows/release.yml, keeper/deploy.ts kubeDeployer). The replacement is on main and off in production: FORGE_RELEASE_KEEPER=swap (docs/features/ship-itself.md). It has never run on a real child; ship-itself.md says so.
Done when:
Needs the owner for cluster access. Files: docs/features/ship-itself.md
Part of #7667 (inventory: docs/PLATFORM.md). Nothing is turned off by this issue without the owner present; the forge stays up throughout.
Parked by the crew: the run ended without a pull: declined: I can't run this drill from here, so no dark-second figures exist and I've pushed nothing.
Parked by the crew: the run ended without a pull: declined: I can't run this drill from here, so there are no dark-second figures and I've pushed nothing.
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: I can't run this drill from here, so no dark-second figures exist and I've pushed nothing
- the run ended without a pull: declined: I can't run this drill from here, so there are no dark-second figures and I've pushed nothing
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #9009. Two runs declined this because no builder can reach a hosted child or have the owner present. #9009 turns the drill into one command, bun scripts/drills/self-swap.ts <forge>, tested against an in-process forge, so the owner can run it and post the four figures. It waits behind the Later gate with the rest of the spin-down (#7667, not urgent) and #8378. #8941 now waits for #9009.
Run the four-step drill from docs/features/ship-itself.md on a hosted child forge, with the owner around: land, swap and verify, a bad release that swaps back by name, a pod restart. Record the seconds dark for each. If a child cannot exercise it, say what is missing.
Done when:
Part of #7667 (inventory: docs/PLATFORM.md). Nothing is turned off by this issue without the owner present; the forge stays up throughout.