A light deploy job, on a core whose gate does not depend on its machine
Build, test, deploy / site (push) Successful in 9m10s

The deploy server is a slow container with other work to do. Its job ran
core's tests, which failed there (no C compiler, no ICU, limits written
for a fast machine), so nothing was published.

- pixi run ci, which the deploy job runs, is the site's tests and core's
  mojo-status-strict at the pinned commit. Core's own tests and
  everything that builds Mojo are core's gate, on a runner of its own;
  pixi run core-test stays for moving the pointer.
- The workflow and docs/deploy.md describe the runner as it is: a new
  container for every job, not a host shell.
- core moves to b10a5c8: a pinned C compiler for the Mojo compiler to
  link with, a Dafny that starts without ICU, time limits at the
  machine's pace, and a prover whose time on the clock is the caller's
  (the Prove tab keeps its 3 seconds).
This commit is contained in:
alexm committed 2026-11-13 06:14:46 -05:00
1 parent e092cb029c
commit 3ebf2e2203
6 files changed
+36 -41

No files matched your search

+16 -13
View File
@@ -1,9 +1,12 @@
# Programming+ on Gitea Actions, with a runner that has no container image: the act_runner runs jobs directly on
# the droplet's shell ("host mode"). docs/deploy.md has the runner's setup, once.
# Programming+ on Gitea Actions. The runner's label `quarto-deploy` names a container image (Node, git, rsync, curl,
# Quarto, pixi) with the droplet's /srv/www bound in, and every job gets a new container: nothing is kept between
# jobs, and everything else the job needs comes from pixi.lock. docs/deploy.md says what the job needs of a runner.
#
# Every push and pull request runs `pixi run ci`, the same task a developer runs, in the environment pixi.lock pins
# (Node, Python, pandoc, Mojo): every test of the site (the Quarto ones fail, not skip, without pandoc), and core's
# tests and mojo-status-strict at the pinned commit. A push to main also checks the chain of pointers
# Every push and pull request runs `pixi run ci` in the environment pixi.lock pins (Node, Python, pandoc, Mojo):
# every test of the site (the Quarto ones fail, not skip, without pandoc), and core's mojo-status-strict at the
# pinned commit. The job is kept light on purpose: the runner is a server with other work. Core's own tests and
# everything that builds Mojo are core's gate, which runs on another runner (core's docs/ci.md); a developer runs
# `pixi run core-test` before moving the pointer. A push to main also checks the chain of pointers
# (`pixi run release-check`) and publishes the site to /srv/www/<slug> as an atomic release (scripts/deploy.sh).
#
# On GitHub Actions the build and test steps run with one change, `runs-on: ubuntu-latest`; the publish step needs
@@ -26,15 +29,15 @@ concurrency:
env:
# set by Gitea and GitHub Actions already; written here so the tests' "fail, not skip, under CI" never depends on it
CI: "true"
# the pixi that reads pixi.lock; when the host has another version, this one is fetched into the cache below
# the pixi that reads pixi.lock; when the runner has another version, this one is fetched into the cache below
PIXI_VERSION: "0.83.0"
jobs:
site:
# a pull request runs only from a branch of this repository: on a host runner a fork's workflow would run its
# own code on the droplet (docs/deploy.md in pplus-web). Drop this line for a runner that is a throwaway VM.
# a pull request runs only from a branch of this repository: a fork's workflow would run its own code in a
# container that can write the droplet's web root (docs/deploy.md). Drop this line for a runner that cannot.
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
# The host-mode label from the runner registration. Jobs run as the runner's user, in a fresh working directory.
# The label from the runner registration: on this runner a container image, new for every job.
runs-on: quarto-deploy
timeout-minutes: 60
steps:
@@ -44,14 +47,14 @@ jobs:
with:
submodules: recursive
# pixi: the host's when it is the pinned version, else the pinned release, fetched once into a cache directory
# the runner's user owns (no sudo), checked by SHA-256
# pixi: the image's when it is the pinned version, else the pinned release, fetched into a cache directory
# (which lasts only where the runner keeps a home between jobs) and checked by SHA-256
- name: pixi, pinned
shell: bash
run: |
set -euo pipefail
if command -v pixi >/dev/null && [ "$(pixi --version | cut -d' ' -f2)" = "$PIXI_VERSION" ]; then
echo "pixi $PIXI_VERSION is on the host: $(command -v pixi)"; exit 0
echo "pixi $PIXI_VERSION is on the PATH: $(command -v pixi)"; exit 0
fi
dir="${PPLUS_CI_CACHE:-$HOME/.cache/pplus-ci}/pixi-$PIXI_VERSION"
if [ ! -x "$dir/pixi" ]; then
@@ -71,7 +74,7 @@ jobs:
- name: The pinned environment, exactly as pixi.lock has it
run: pixi install --locked
# every test of the site; core's tests and mojo-status-strict at the pinned commit (pixi.toml)
# every test of the site, and core's mojo-status-strict at the pinned commit (pixi.toml)
- name: pixi run ci
run: pixi run ci