ci: install each published build into the paseo host mount #31
No reviewers
Labels
No labels
code-review
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
sam/brainless!31
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/install-into-paseo-mount"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Adds a step to
.forgejo/workflows/build.ymlthat installs the build this run just published into the host directory the paseo container runs brainless from.Why
sam/pi-deployis moving brainless out of the paseo image: the container runs the binary bind-mounted from the host at/opt/brainless(mount ofdata/brainless, added in pi-deploy PR #73). That makes a brainless update a file replacement instead of an image rebuild — but the replacement has to happen somewhere. pi-deploy's deploy workflow does it when that repository is pushed; this step does it when this one is pushed, which is the moment a new binary exists. The daemon spawns brainless once per agent session, so the next session runs it, with no container restart and no interrupted turn.How
latestrelease serves.ETXTBSY); a rename also leaves sessions already running on the bytes they started with.scripts/update-brainless.sh), so a broken build cannot put a stub in the container./home/sam/git/sam/pi-deployis absent, i.e. on any runner other than this Pi's (thelinux:hostrunner is shared, and this path is the same one the pi-deploy deploy workflow already relies on).Verified
0755with its sha256 reported; a re-run installed again; a 12-byte file and a 2 MB non-ELF file each exited 1 and left the previously installed binary untouched; an absent mount path printed the skip and exited 0.Coupling
This hardcodes one host path into this repository's CI. That is the trade for not polling: this repository knows exactly when a new binary exists, and the runner already has the path mounted. If pi-deploy's mount moves, this step silently skips (it only tests for the directory), so the pi-deploy script remains the path that always works.