Unsupervised/unsupervised-scheduler
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 19 Wiki Activity

CI: publish prebuilt CI images to the Gitea container registry #188

Merged
thatguygriff merged 1 commits from feature/187-ci-container-images into main 2026-08-25 01:05:35 +00:00
Conversation 0 Commits 1 Files Changed 3
+224
1 Commits
Author SHA1 Message Date
thatguygriffandClaude Opus 5 572aaf5b49 Publish prebuilt CI images to the Gitea container registry
CI Images / Build CI image (PHP 8.2) (pull_request) Successful in 1m14s
Details
CI Images / Build CI image (PHP 8.1) (pull_request) Successful in 1m26s
Details
CI Images / Build CI image (PHP 8.3) (pull_request) Successful in 2m3s
Details
CI Images / Build CI image (PHP 8.5) (pull_request) Successful in 2m9s
Details
CI / Tests (PHP 8.2) (pull_request) Successful in 1m7s
Details
CI / No Debug Code (pull_request) Successful in 2s
Details
CI / Tests (PHP 8.3) (pull_request) Successful in 3m8s
Details
CI / Tests (PHP 8.1) (pull_request) Successful in 5m55s
Details
CI / Tests (PHP 8.5) (pull_request) Successful in 6m21s
Details
CI / Coding Standards & Static Analysis (pull_request) Successful in 18m26s
Details
CI / Build Plugin Zip (pull_request) Skipped
Details 
setup-php installs PHP 8.3+ from apt on these arm64 runners: a ~145s floor
against ~35s for 8.1/8.2, with a tail that twice ran past the step timeout
and failed the run (#178). Caching the .debs softened it without removing
the apt step, and 8.5 has the same problem.

Add a per-version CI image built on php:<version>-cli-alpine and a workflow
that publishes it to git.unsupervised.ca/unsupervised/ci-php:<version>. The
org is public, so the packages pull anonymously.

The image carries bash and nodejs because act_runner runs JavaScript actions
inside the job container, GNU coreutils/grep/sed because the workflow scripts
use `tac` and `grep --include`, and curl/jq/git/zip for release.yml and
bin/build-zip.sh. Composer 2 and the intl and zip extensions round it out.

Nothing consumes the images yet — ci.yml and release.yml switch over in a
follow-up, because a job cannot run in an image that has not been published.

Part of #187

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01D9acV1mHktGAb1uyvNmrR2
 2026-08-24 21:55:28 -03:00