reseam/ci
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
2 commits 1 branch 0 tags 42 KiB
  • Dockerfile 100%
Find a file
Exact
Aunali321 d3852f900c fix: give the ci user a tool cache for setup actions
2026-10-19 21:50:43 +05:30
Dockerfile fix: give the ci user a tool cache for setup actions 2026-10-19 21:50:43 +05:30
LICENSE feat: add the CI image Reseam repositories build and release in 2026-10-19 20:45:19 +05:30
NOTICE feat: add the CI image Reseam repositories build and release in 2026-10-19 20:45:19 +05:30
README.md feat: add the CI image Reseam repositories build and release in 2026-10-19 20:45:19 +05:30

README.md

Reseam logo

Reseam CI

The image Reseam's repositories build and release in, published at ghcr.io/reseam/ci. It runs on any forge whose runner can pull a public image: GitHub, Forgejo, Codeberg.

It is Ubuntu 24.04 with:

  • Java 17 and 21, Node.js, Bun, just
  • The Android SDK platforms 35, 36 and 37, build-tools 35 and 36, and the NDK
  • Rust with the Android, Windows and WASI targets, BoltFFI, llvm-mingw and a Windows JDK for the Windows CLI, and the WASI SDK
  • The Linux and Windows packaging tools: dpkg, rpm, makepkg, NSIS

Versions are pinned as ARGs in the Dockerfile. Jobs run as ci (uid 1001, the uid of GitHub's runner user), with passwordless sudo. The SDK is read-only, so a build that needs a package the image lacks fails instead of downloading it.

How repositories use it

Each repository has a justfile and one workflow, .github/workflows/ci.yml, that runs just check and then just release <tag> in this image on v* tags. just release publishes with reseam release.

On Forgejo, the organization variable RUNNER names the runner label. GitHub falls back to ubuntu-latest.

Publish

docker build -t ghcr.io/reseam/ci:<yyyy.mm.dd> .
docker push ghcr.io/reseam/ci:<yyyy.mm.dd>

Then point each repository's ci.yml at the new tag.

License

AGPL-3.0-or-later, with additional terms under section 7 in NOTICE.