rajames/LithosAnanke
1
1
Fork 0
Code Issues 43 Pull Requests 1 Actions Packages Projects Releases Activity

CI: a runner image with the build's tools already installed #120

New Issue
Open
opened 2026-11-06 20:42:31 +00:00 by rajames · 0 comments
rajames commented 2026-11-06 20:42:31 +00:00
Owner
Copy Link
Copy Source

What

An image, built from gitea/runner-images:ubuntu-24.04, with what make ARCH=amd64,aarch64,riscv64 init INIT_DOCS=0 installs (and Maven, for the publish steps) already in it, kept in this repository's package registry. The workflows name it as their container.

Why

Captain Bob, 2026-11-06: a small server, a little sluggish. Each change costs about an hour of runner time, of which the gate itself (acceptance) is about 15 minutes. Every job starts by installing the same packages: ~2-3 minutes, five times per change.

Done when

  • The image's recipe is in the tree, its package list taken from the Makefile's init, not copied
  • A workflow builds and publishes it to the package registry
  • The workflows run in it; their install step takes seconds
  • Acceptance passes in it
## What An image, built from `gitea/runner-images:ubuntu-24.04`, with what `make ARCH=amd64,aarch64,riscv64 init INIT_DOCS=0` installs (and Maven, for the publish steps) already in it, kept in this repository's package registry. The workflows name it as their container. ## Why Captain Bob, 2026-11-06: a small server, a little sluggish. Each change costs about an hour of runner time, of which the gate itself (acceptance) is about 15 minutes. Every job starts by installing the same packages: ~2-3 minutes, five times per change. ## Done when - [ ] The image's recipe is in the tree, its package list taken from the Makefile's `init`, not copied - [ ] A workflow builds and publishes it to the package registry - [ ] The workflows run in it; their install step takes seconds - [ ] Acceptance passes in it
rajames added this to the CI and the gate milestone 2026-11-06 20:42:31 +00:00
rajames added the
priority
should
status
in-progress
kind
ci
 labels 2026-11-06 20:42:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/capsules
capsules/ and mkcapsule
 area/docs
docs/
 area/kernel
kernel/ -- LithosAnanke
 area/proofs
proof/ -- Isabelle/HOL
 area/v3
v3/ -- the original StarForth VM
 area/v4
v4/ and capsules/v4 -- the F18 engine
 board/milkv
Milk-V Mars
 board/pc
Generic x86-64 PC (SER5)
 board/raspi4
Raspberry Pi 4 (not ported)
 board/raspi5
Raspberry Pi 5
 board/zynq7020
Zynq-7020 (ARMv7 port in progress)
kind
bug
Something is wrong
kind
chore
Housekeeping, repo hygiene
kind
ci
Build, CI, nightly, release
kind
docs
Documentation only
kind
feature
New capability
priority
must
Needed for v4.0.0 (JUSTIFICATION.md 14/16)
priority
nice
Nice to have
priority
should
Needed for the product, not for the tag
status
backlog
Not started
status
blocked
Waiting on something else
status
in-progress
Being worked on
status
needs-acceptance
Done; the QEMU acceptance boots are still to run
status
rejected
Decided against; closed
No labels
kind
ci
priority
should
status
in-progress
Milestone
No items
No Milestone CI and the gate
Projects
Clear projects
No projects
Assignees
Clear assignees
rajames (Robert A. James (Captain Bob))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rajames/LithosAnanke#120