You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
installer: add Dakota-style offline ISO build, install, and boot CI #14
Turn the local Utah ISO implementation into a published, evidence-producing pipeline based on Dakota's modern ISO workflow. Build the production ISO, boot it, perform a complete network-isolated installation from the embedded OCI payload, and boot the installed system graphically.
Acceptance criteria
CI builds the production x86_64 UEFI ISO and SHA-256 checksum.
A live-boot gate observes the Utah ready marker and captures serial output and a screenshot.
A network-isolated fisherman installation completes from the embedded payload.
The installed disk boots to graphical target and preserves Utah identity.
ISO upload/publication occurs only after every production gate passes.
Failure runs retain serial logs, screenshots, and the failed disk image for diagnosis.
Picked up this issue. The Dakota-style offline ISO build/install/boot CI already largely landed in main via the LUKS E2E pipeline in post-testing-e2e.yml (ISO + SHA-256, network-isolated fisherman install from the embedded payload, graphical installed boot with Utah identity, publish-after-gate, and failure diagnostics). The one acceptance criterion not yet covered — 'A live-boot gate observes the Utah ready marker' — is addressed by PR #229, which asserts the UTAH_LIVE_READY serial marker in the live-boot gate (iso/scripts/luks-e2e.sh) in addition to graphical.target.
The requested 'Dakota-style offline ISO build, install, and boot CI' is already implemented in .github/workflows/post-testing-e2e.yml, leveraging iso/scripts/luks-e2e.sh for validation and providing production-iso artifacts as described in docs/skills/ci-workflows.md. This work was introduced in PRs #84 and #198.
Activity
mendezr commentedon Sep 21, 2026
Picked up this issue. The Dakota-style offline ISO build/install/boot CI already largely landed in main via the LUKS E2E pipeline in post-testing-e2e.yml (ISO + SHA-256, network-isolated fisherman install from the embedded payload, graphical installed boot with Utah identity, publish-after-gate, and failure diagnostics). The one acceptance criterion not yet covered — 'A live-boot gate observes the Utah ready marker' — is addressed by PR #229, which asserts the UTAH_LIVE_READY serial marker in the live-boot gate (iso/scripts/luks-e2e.sh) in addition to graphical.target.
— hive: backend=goose model=deepseek/deepseek-v4-flash-0731
🐝 Hive Agent:
contributor| SHA:4723139mendezr commentedon Sep 25, 2026
The requested 'Dakota-style offline ISO build, install, and boot CI' is already implemented in .github/workflows/post-testing-e2e.yml, leveraging iso/scripts/luks-e2e.sh for validation and providing production-iso artifacts as described in docs/skills/ci-workflows.md. This work was introduced in PRs #84 and #198.
— hive: backend=pi model=openrouter/google/gemma-4-31b-it
🐝 Hive Agent:
contributor| SHA:369e3f2castrojo commentedon Sep 26, 2026
Closing as completed: resolved by PRs #84, #198, and #229, implementing offline ISO build/boot CI and gating on the
UTAH_LIVE_READYmarker.