A light deploy job, on a core whose gate does not depend on its machine
Build, test, deploy / site (push) Successful in 9m10s
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:
6 files changed
+36
-41
No files matched your search
@@ -35,7 +35,7 @@ Every command is a pixi task (`pixi task list` shows them with their description
|
||||
| **Build and test the site** | |
|
||||
| `install` | Install TypeScript, the only npm dependency |
|
||||
| `core-build` | Build pplus-core (`core/`) into `core/dist/`, which the site imports as `#core/` |
|
||||
| `core-test` | Run pplus-core's own tests |
|
||||
| `core-test` | Run pplus-core's own tests at the pinned commit, before moving the pointer (the deploy job does not run them) |
|
||||
| `core-status` | Core's `mojo-status-strict` at the pinned commit: no Mojo program of ours fails (offline) |
|
||||
| `build` | Build core, then compile `src/` to `dist/` |
|
||||
| `watch` | Rebuild `dist/` on every change |
|
||||
@@ -49,7 +49,7 @@ Every command is a pixi task (`pixi task list` shows them with their description
|
||||
| `quarto-engine <dir>` | Copy a built Programming+ and core into a site's `_extensions/pplus/engine`, for the rendered views ([quarto/README.md](quarto/README.md)) |
|
||||
| `quarto-example` | Render the example site in `quarto/example`, every shortcode on real pages (needs Quarto) |
|
||||
| **Ship** ([docs/deploy.md](docs/deploy.md)) | |
|
||||
| `ci` | What CI runs: every test of the site, against the pinned core |
|
||||
| `ci` | What the deploy job runs before it publishes: every test of the site, and core's `mojo-status-strict` at the pinned commit |
|
||||
| `release-check` | Is the chain web → core → library consistent: each pointer checked out, clean and on its pushed branch, generated files current, Mojo pinned alike |
|
||||
| `release-bump` | After a change in `core/library` or `core`: move the pointers bottom up, regenerate, run each gate, print what to push in order (`--commit` commits; nothing pushes) |
|
||||
| `site` | Test, then assemble `site/` |
|
||||
|
||||
Reference in new issue
Block a user