Files
LithosAnanke/.gitea/workflows/nightly-docs.yml
T
rajamesandClaude Opus 5.5 6eadd2f56c
Build / Image RASPI (push) Successful in 4m20s
Build / Image PC (push) Successful in 3m56s
Build / Image MILKV (push) Successful in 4m2s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 11m5s
Build / Image RASPI (pull_request) Successful in 4m33s
Build / Image PC (pull_request) Successful in 4m24s
Build / Image MILKV (pull_request) Successful in 5m4s
Build / v4 tests (32- and 64-bit cells) (pull_request) Successful in 11m54s
ci: build.yml checks every push and PR; every job on Ubuntu 24.04 with Node (closes #18)
build.yml, as master had it, could not run here: it called
Makefile.starkernel and make T=<board> (the tree has kernel/Makefile
and TARGET=<board>), listed a Pi 4 with no port, published "releases"
under org/f18 on every push, installed Isabelle2024 (the proofs need
Isabelle2025-2) from a mirror that answered 503, and duplicated the
nightlies with its own 02:00 schedule. Now it is the check on every
push to master and StarForth-v4.0.0 and every PR into master: each
board's image (make boot_image TARGET=PC|RASPI|MILKV, xz'd, kept with
its SBOM) and make -C v4 test, both cell widths. It publishes nothing;
the nightlies and release.yml do.

Every job of every workflow now names its container,
gitea/runner-images:ubuntu-24.04-v26.11.03: the runner maps
ubuntu-latest to node:20-bullseye, Debian 11, where every job of PR
#30's runs failed at its first apt-get, and which has no
qemu-efi-riscv64 and a far older QEMU and compilers than the Ubuntu
24.04 all of this was tested on. Node is needed in the image:
actions/checkout and upload-artifact run inside the job's container.
The dated tag keeps a run from changing under an image update.

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

49 lines
1.6 KiB
YAML

# Nightly snapshot of the documents: the book, the formal volumes and the API reference
# (scripts/nightly.sh docs), then Nexus.
#
# org.starship:documentation:<LITHOS_VERSION>-SNAPSHOT, starshipos-snapshots
# classifier book the book (make docs)
# classifier vol1, vol2, vol3 the formal volumes (make -C docs/formal vols)
# classifier api the API reference (make -C docs/formal doxygen)
#
# Gitea runs a schedule from the default branch, master, so this builds master.
name: Nightly documents
on:
schedule:
- cron: '0 4 * * *' # 04:00 UTC, after the images (nightly.yml, 03:00)
workflow_dispatch:
jobs:
docs:
name: Book, volumes, API reference
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: 90
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
lfs: false
- name: Install the documents' dependencies
run: |
make ARCH=amd64 init INIT_PROOFS=0
DEBIAN_FRONTEND=noninteractive apt-get install -y -qq maven default-jre-headless
- name: Documents
run: scripts/nightly.sh docs
- name: Publish to Nexus
env:
NEXUS_USER: ci-publisher
NEXUS_PASSWORD: ${{ secrets.NEXUS_CI_PASSWORD }}
run: scripts/nightly.sh publish-docs https://nexus.starshipos-f18.org/repository/starshipos-snapshots
- name: Keep the documents
uses: actions/upload-artifact@v3
with:
name: documents-${{ github.run_number }}
path: build/nightly-docs/