Files
LithosAnanke/.gitea/workflows/build.yml
T
rajamesandClaude Opus 5.5 0fd7648a77
Build / Image RASPI (push) Successful in 4m19s
Build / Image PC (push) Successful in 4m14s
Build / Image MILKV (push) Successful in 4m30s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 11m19s
Acceptance / Acceptance (pull_request) Successful in 16m48s
ci: acceptance.yml gates every PR into master; master only through an accepted PR
Captain Bob, 2026-11-06: what a developer runs, what CI runs and what
the nightly runs are one process, and "failures should not be allowed
to be merged to master".

acceptance.yml runs on every PR into master (opened, pushed to,
reopened): .claude/CLAUDE.md's acceptance protocol through the same
scripts/nightly.sh stages -- amd64, aarch64, riscv64 to [zuse@Hera]
ok>, the PC stick loaded high (and the three agree on dict_hash), then
make -C v4 test-32 -- one QEMU at a time, in one job. Its logs and DoE
CSVs are kept, pass or fail. master's branch protection requires it.

acceptance, nightly and release share the concurrency group qemu, so
the runner never runs two of them at once: CLAUDE.md's one-QEMU rule
holds in CI too. build.yml becomes the quick check on pushes only.

.claude/CLAUDE.md's Hard Rules: commit and push directly on the working
branch; master only through a PR that passed acceptance, no direct
pushes; no approval required while there is one developer. Named: the
Captain Bob method.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 16:24:22 +00:00

66 lines
2.4 KiB
YAML

# The quick check on every push: each board's image builds, and the v4 tests pass. A pull
# request into master is gated by acceptance.yml, the full acceptance protocol.
# Nothing is published here. The nightlies own the rest: nightly.yml (the QEMU acceptance boots,
# the 32-bit build, the Isabelle/HOL proofs, the images to Nexus) and nightly-docs.yml (the
# documents to Nexus).
name: Build
on:
push:
branches: [master, StarForth-v4.0.0]
workflow_dispatch:
jobs:
image:
name: Image ${{ matrix.board }}
runs-on: ubuntu-latest
container:
image: gitea/runner-images:ubuntu-24.04-v26.11.03 # the runner's own ubuntu-latest is Debian 11 (node:20-bullseye)
timeout-minutes: 45
strategy:
fail-fast: false
matrix:
include: # boards/<dir>/board.mk; Pi 4 has no port yet (#26)
- { board: PC, arch: amd64, dir: pc, image: lithos-pc.img }
- { board: RASPI, arch: aarch64, dir: raspi, image: lithos-raspi.img }
- { board: MILKV, arch: riscv64, dir: milkv, image: lithos-milkv.img }
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # the SBOM's version is git describe
lfs: false # only the logs and DoE CSVs are in LFS; the build needs neither
- name: Install the build's dependencies
run: make ARCH=${{ matrix.arch }} init INIT_DOCS=0
- name: Boot image
run: make boot_image TARGET=${{ matrix.board }}
- name: Compress # the PC image is a 2 GiB stick, nearly all empty
run: xz -T0 -6 build/boards/${{ matrix.dir }}/${{ matrix.image }}
- name: Keep the image and its SBOM
uses: actions/upload-artifact@v3
with:
name: image-${{ matrix.dir }}-${{ github.run_number }}
path: |
build/boards/${{ matrix.dir }}/${{ matrix.image }}.xz
build/boards/${{ matrix.dir }}/*.spdx*
v4-tests:
name: v4 tests (32- and 64-bit cells)
runs-on: ubuntu-latest
container:
image: gitea/runner-images:ubuntu-24.04-v26.11.03 # the runner's own ubuntu-latest is Debian 11 (node:20-bullseye)
timeout-minutes: 60
steps:
- uses: actions/checkout@v4
with:
lfs: false
- name: Install the build's dependencies
run: make ARCH=amd64 init INIT_DOCS=0
- name: make -C v4 test
run: make -C v4 test