WIP: Build appliance EFI through its retained producer #550

Draft
erikinkinen wants to merge 3 commits from feature/retained-efi-image-build into feature/retained-image-manifest-inputs
Owner

Use the original retained Cargo/PE producer for appliance EFI builds, with explicit source/catalog/tool/storage selections and finite bounds. The appliance feature policy is preserved; debug selects Cargo dev and release selects release. No generated Cargo environment or source-tree EFI fallback is used.

Retained packaging requires the separate original host Boot-tool/ESP bridge before producers start, then passes the actual external PE path and separate host executable output to it. The ESP path is explicit. Legacy packaging remains available.

Depends on #549.

  • Add explicit EFI producer dispatch and preserve producer failures.
  • Bypass legacy EFI environment and source-tree output assumptions in retained packaging.
  • Compose the separate host/ESP bridge and complete the appliance image.

The EFI product is PE file data, not an ELF shared-library provenance record. This change does not certify an image or guest workload.

Use the original retained Cargo/PE producer for appliance EFI builds, with explicit source/catalog/tool/storage selections and finite bounds. The appliance feature policy is preserved; debug selects Cargo dev and release selects release. No generated Cargo environment or source-tree EFI fallback is used. Retained packaging requires the separate original host Boot-tool/ESP bridge before producers start, then passes the actual external PE path and separate host executable output to it. The ESP path is explicit. Legacy packaging remains available. Depends on #549. - [x] Add explicit EFI producer dispatch and preserve producer failures. - [x] Bypass legacy EFI environment and source-tree output assumptions in retained packaging. - [ ] Compose the separate host/ESP bridge and complete the appliance image. The EFI product is PE file data, not an ELF shared-library provenance record. This change does not certify an image or guest workload.
feat: Build appliance EFI through its retained producer
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / host_two (push) Has been cancelled
CI / host_three (push) Has been cancelled
CI / integration (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
Markdown / markdown (push) Has been cancelled
0faf3bb13d
erikinkinen added this to the Alpha 1 milestone 2026-11-07 23:47:27 +01:00
fix: Refuse relative image outputs before production
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / host_two (push) Has been cancelled
CI / host_three (push) Has been cancelled
CI / integration (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
Markdown / markdown (push) Has been cancelled
2c0fadf105
Author
Owner

The retained EFI bridge now produces a fresh x86-64 EFI application from the actual catalog-selected Bootloader, with the appliance console feature and Cargo dev profile. The original PE checks pass, including the zero COFF timestamp, and the original source, compiler and publication owners retire cleanly.

The separate host Boot-tool/ESP bridge is still needed for image packaging. This milestone does not establish byte reproducibility or firmware execution.

The retained EFI bridge now produces a fresh x86-64 EFI application from the actual catalog-selected Bootloader, with the appliance console feature and Cargo dev profile. The original PE checks pass, including the zero COFF timestamp, and the original source, compiler and publication owners retire cleanly. The separate host Boot-tool/ESP bridge is still needed for image packaging. This milestone does not establish byte reproducibility or firmware execution.
docs: Define EFI reproducibility scope for each profile
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
Markdown / markdown (push) Failing after 11s
Coreutils provider graph / coreutils (push) Successful in 4m28s
CI / rust (push) Failing after 6m48s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / host_two (push) Has been skipped
CI / host_three (push) Has been skipped
CI / integration (push) Has been skipped
a214c48acb
Author
Owner

Two fresh retained EFI builds using the unchanged packaged release profile and console feature produce identical PE bytes: 170,496 bytes, SHA-256 db1a75e062c4eb8714fed9a75d374ce0ed5dec205944434ab5b1375e495f43a1. Both original operations finish within their existing bounds and retire cleanly.

Development builds retain full debugging and a matching PDB. Their debug identifier still depends on fresh build paths; the guide now explains that limitation. The release comparison does not establish development/PDB reproducibility, firmware execution or complete-image acceptance.

Two fresh retained EFI builds using the unchanged packaged release profile and console feature produce identical PE bytes: 170,496 bytes, SHA-256 `db1a75e062c4eb8714fed9a75d374ce0ed5dec205944434ab5b1375e495f43a1`. Both original operations finish within their existing bounds and retire cleanly. Development builds retain full debugging and a matching PDB. Their debug identifier still depends on fresh build paths; the guide now explains that limitation. The release comparison does not establish development/PDB reproducibility, firmware execution or complete-image acceptance.
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
Markdown / markdown (push) Failing after 11s
Coreutils provider graph / coreutils (push) Successful in 4m28s
CI / rust (push) Failing after 6m48s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / host_two (push) Has been skipped
CI / host_three (push) Has been skipped
CI / integration (push) Has been skipped
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/retained-efi-image-build:feature/retained-efi-image-build'
git switch 'feature/retained-efi-image-build'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/retained-image-manifest-inputs'
git merge --no-ff 'feature/retained-efi-image-build'
git switch 'feature/retained-efi-image-build'
git rebase 'feature/retained-image-manifest-inputs'
git switch 'feature/retained-image-manifest-inputs'
git merge --ff-only 'feature/retained-efi-image-build'
git switch 'feature/retained-efi-image-build'
git rebase 'feature/retained-image-manifest-inputs'
git switch 'feature/retained-image-manifest-inputs'
git merge --no-ff 'feature/retained-efi-image-build'
git switch 'feature/retained-image-manifest-inputs'
git merge --squash 'feature/retained-efi-image-build'
git switch 'feature/retained-image-manifest-inputs'
git merge --ff-only 'feature/retained-efi-image-build'
git switch 'feature/retained-image-manifest-inputs'
git merge 'feature/retained-efi-image-build'
git push origin 'feature/retained-image-manifest-inputs'
Sign in to join this conversation.
No description provided.