Files
forgefirm/.github/workflows/yocto-cold-build.yml
T
ScottW514 0a05b6b114 docs: present-state build and update docs; fix the ring-size arithmetic
- kas/README.md: the real-time rationale rests on the feeder's bounded
  queue depth, not ring size; the ring is 16 MiB (~84 s at 200 kHz,
  ~28 min at the 10 kHz cloud tick), a capacity for cloud-mode preload.
- BUILD.md, kas config, release checklist, cold-build workflow: only
  forgefirm and meta-openglow (branch scarthgap) are cloned as
  siblings; every ForgeFIRM source repo is fetched by pinned SRCREV.
- UPDATE-SYSTEM.md reads as the present-state design: the cloud-mode
  compatibility baseline is the cloud client's configured firmware
  version, not release metadata; decisions and open items listed
  plainly.
- README.md states what GRBL mode still needs the Glowforge service
  for (camera-referenced homing) and what runs without it.
- BRINGUP.md: generic build-host and fwup-lab references, the retained
  reproductions of the no-fire drill, the System tab.
- LIGHTBURN.md: the arm-window timeouts are machine settings.
- forgefirm-image.bb describes forgectrl as the machine-services
  daemon and points at the right backlog entry.
- American spelling throughout.
2026-08-15 06:12:51 -04:00

72 lines
2.6 KiB
YAML

# Cold-build reproducibility probe: proves a fresh clone still builds the
# release image, and publishes the artifact checksums for comparison
# against locally built releases. Dispatch-only - releases are built and
# signed on the maintainer's build host (see docs/UPDATE-SYSTEM.md); this
# workflow never produces release artifacts.
#
# A cold Yocto build on a 4-core hosted runner takes hours and lives
# close to the 6-hour job cap; a timeout here is a data point, not an
# emergency.
name: yocto-cold-build
on:
workflow_dispatch:
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 360
steps:
- name: Reclaim runner disk
run: |
sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc \
/opt/hostedtoolcache/CodeQL /usr/local/.ghcup \
/usr/local/share/boost
df -h /
- name: Checkout forgefirm
uses: actions/checkout@v4
with:
path: forgefirm
# The kas config references meta-openglow as a local sibling
# (kas/README.md "Push & release order" step 4 flips it to the
# pinned-remote block at release time). Every source repo the recipes
# build is fetched by pinned SRCREV; no other sibling is needed.
- name: Checkout meta-openglow (sibling)
uses: actions/checkout@v4
with:
repository: ScottW514/meta-openglow
ref: scarthgap
path: meta-openglow
- name: Host dependencies
run: |
sudo apt-get update -qq
sudo apt-get install -y -qq gawk wget git diffstat unzip texinfo \
gcc build-essential chrpath socat cpio python3 python3-pip \
python3-pexpect xz-utils debianutils iputils-ping python3-git \
python3-jinja2 zstd liblz4-tool file locales libacl1
sudo locale-gen en_US.UTF-8
pip3 install kas
- name: Build (rm_work, release image only)
working-directory: forgefirm
run: kas build kas/forgefirm-glowforge.yml:kas/ci.yml
- name: Checksums
working-directory: forgefirm
run: |
cd build/tmp/deploy/images/glowforge
sha256sum $(readlink forgefirm-image-glowforge.rootfs.ext4) \
$(readlink forgefirm-image-glowforge.rootfs.wic.gz) \
| tee cold-build-checksums.txt "$GITHUB_STEP_SUMMARY"
- name: Upload checksums
uses: actions/upload-artifact@v4
with:
name: cold-build-checksums
path: forgefirm/build/tmp/deploy/images/glowforge/cold-build-checksums.txt
retention-days: 90