feat(images): add the ci-base job image for CI runners #3

Merged
crapougnax merged 1 commit from feat/ci-base-image into develop 2026-11-14 11:00:19 +00:00
Owner

Runners deployed by the forgejo-runner recipe are ephemeral: every job
pulls a generic image, then installs its tools again. ci-base ships them
once: Node.js 22 with Corepack, Bun, Git LFS, a C/C++ toolchain and
Python 3, the Docker CLI with Buildx, the PostgreSQL client and common
utilities, on node:22-bookworm-slim.

  • images/ci-base/Containerfile: versions pinned through build
    arguments, OCI labels, unprivileged user by default;
  • images/ci-base/VERSION: version of the image (1.0.0), independent of
    the catalogue tags; a released version is never overwritten;
  • images/ci-base/smoke-test.sh: checks every tool inside the image;
  • workflow: build and smoke test on pull requests, multi-architecture
    publication (amd64, arm64) from develop and main, to the registry
    named by the repository variable IMAGE_REGISTRY;
  • README in English and French: content, tags, usage.

The forgejo-runner recipe is unchanged: no rendered manifest changes.

Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com

Runners deployed by the forgejo-runner recipe are ephemeral: every job pulls a generic image, then installs its tools again. ci-base ships them once: Node.js 22 with Corepack, Bun, Git LFS, a C/C++ toolchain and Python 3, the Docker CLI with Buildx, the PostgreSQL client and common utilities, on node:22-bookworm-slim. - images/ci-base/Containerfile: versions pinned through build arguments, OCI labels, unprivileged user by default; - images/ci-base/VERSION: version of the image (1.0.0), independent of the catalogue tags; a released version is never overwritten; - images/ci-base/smoke-test.sh: checks every tool inside the image; - workflow: build and smoke test on pull requests, multi-architecture publication (amd64, arm64) from develop and main, to the registry named by the repository variable IMAGE_REGISTRY; - README in English and French: content, tags, usage. The forgejo-runner recipe is unchanged: no rendered manifest changes. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(images): add the ci-base job image for CI runners
Some checks failed
CI / CI (pull_request) Failing after 38s
CI base image / Build, test and publish ci-base (pull_request) Successful in 1m19s
7a88140027
Runners deployed by the forgejo-runner recipe are ephemeral: every job
pulls a generic image, then installs its tools again. ci-base ships them
once: Node.js 22 with Corepack, Bun, Git LFS, a C/C++ toolchain and
Python 3, the Docker CLI with Buildx, the PostgreSQL client and common
utilities, on node:22-bookworm-slim.

- images/ci-base/Containerfile: versions pinned through build
  arguments, OCI labels, unprivileged user by default;
- images/ci-base/VERSION: version of the image (1.0.0), independent of
  the catalogue tags; a released version is never overwritten;
- images/ci-base/smoke-test.sh: checks every tool inside the image;
- workflow: build and smoke test on pull requests, multi-architecture
  publication (amd64, arm64) from develop and main, to the registry
  named by the repository variable IMAGE_REGISTRY;
- README in English and French: content, tags, usage.

The forgejo-runner recipe is unchanged: no rendered manifest changes.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
crapougnax merged commit f6e7fd61dd into develop 2026-11-14 11:00:19 +00:00
crapougnax deleted branch feat/ci-base-image 2026-11-14 11:00:20 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/catalog!3
No description provided.