CI fallback: the Stalwart compatibility job on Gitea's own runners #64

Merged

jcoffey-dev merged 1 commits from ci/stalwart-gitea-fallback into main

2026-10-27 07:05:11 +00:00

jcoffey-dev commented

2026-10-27 07:03:05 +00:00

Owner

The Gitea half of #63: the same stalwart check for when BUILD_ON is unset.

Runs on docker (the socket), starts Stalwart as a sibling on ci-net, and copies the checkout into a node:26 container to run stalwart-compat.test.ts, since the job workspace is not on the host.
The image runs Stalwart's binary directly and its user can't write /etc/stalwart, so the config that keeps it out of bootstrap mode goes to /tmp and is passed with --config.
Both containers are removed when the step ends; the recovery admin password is random per run and masked.

Tested on the real runner from a throwaway branch (since deleted): both matrix jobs on host3-docker, Tests 4 passed (4) on 0.16.27 and 1.0.0.

With BUILD_ON=github this job skips, like the other build jobs.

The Gitea half of #63: the same `stalwart` check for when `BUILD_ON` is unset. - Runs on `docker` (the socket), starts Stalwart as a sibling on `ci-net`, and copies the checkout into a `node:26` container to run `stalwart-compat.test.ts`, since the job workspace is not on the host. - The image runs Stalwart's binary directly and its user can't write `/etc/stalwart`, so the config that keeps it out of bootstrap mode goes to `/tmp` and is passed with `--config`. - Both containers are removed when the step ends; the recovery admin password is random per run and masked. Tested on the real runner from a throwaway branch (since deleted): both matrix jobs on host3-docker, `Tests 4 passed (4)` on 0.16.27 and 1.0.0. With `BUILD_ON=github` this job skips, like the other build jobs.

jcoffey-dev added 1 commit 2026-10-27 07:03:05 +00:00

CI fallback: the Stalwart compatibility job on Gitea's own runners

ci / node (pull_request) Skipped

Details

ci / version (pull_request) Skipped

Details

ci / stalwart (stalwartlabs/stalwart@sha256:baafeacd6cbde77acdd94af49972d41c6709e54a376df48e18a9fe3f445eb3d5, 1.0.0) (pull_request) Skipped

Details

ci / stalwart (stalwartlabs/stalwart@sha256:c429b311c93db5606598abc1c68225a85a6953183848ae01bee9c6a98885836c, 0.16.27) (pull_request) Skipped

Details

ci / docker-build (pull_request) Skipped

Details

ci / publish (pull_request) Skipped

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 1m46s

Details

7f98b9947d

The same check as GitHub ci.yml's stalwart job, for when BUILD_ON is unset.
It runs on `docker`, starts Stalwart beside the job on ci-net and copies the
checkout into a node container, since the workspace isn't on the host. Run
once on host3-docker from a throwaway branch: 4/4 on 0.16.27 and on 1.0.0.

jcoffey-dev merged commit a4d14ef1f9 into main

2026-10-27 07:05:11 +00:00

jcoffey-dev deleted branch ci/stalwart-gitea-fallback

2026-10-27 07:05:11 +00:00

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coffey-labs/ihasmail#64