CI with JDK21 and activate tests #1

2026-09-11T05:15:46+02:00

mi commented

2026-09-11 05:15:46 +02:00

No description provided.

mi added 2 commits 2026-09-11 05:15:46 +02:00

build: compile with the build environment's JDK, target Java 17 d53b8f33b0

The toolchain block demanded a JDK 17 installation. Werkdock's build
environment has JDK 21 and nothing else, so CI could not resolve it and
never got as far as compiling.

Raising the toolchain to 21 would have been the wrong fix: the managed
webspace tools/deploy.sh copies the result to runs Java 17, and Java 21
bytecode would not start there. Those are two separate things, and
options.release separates them — compile with whatever JDK is present,
emit class files a Java 17 runtime accepts (verified: major version 61).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

ci: run the container tests, now that werkdock serves the API 680f450462

Until werkdock 0.6.0 the CI build could only compile and assemble: the
tests need a Docker API socket and a postgres image, and the build
sandbox had neither. Both exist now on the instance — the socket is
served into this repository's build-environment home, which Werkator's
werkdock runner already binds into every sandbox as /root, so no mount
and no Werkator change is needed to reach it.

Ryuk stays disabled: it wants an API socket inside a container of its
own, which werkdock does not offer. build/reports joins the artifacts
so a failing test is readable from the build page.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mi changed title from ~~CI with Jdk21~~ to CI with JDK21 and activate tests

2026-09-11 05:16:15 +02:00

mi merged commit 8bf8fd61ec into main

2026-09-11 05:16:51 +02:00

mi deleted branch ci-jdk21-release17

2026-09-11 05:16:51 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mi/werkprobe#1