Run Forgejo Android CI from a pinned BookWave image #53
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/bookwave-ci-image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Replace repeated Android/JDK bootstrap work in Forgejo CI with one reusable, repository-owned BookWave Android CI image.
This PR is the complete CI-image slice. It does not include persistent Gradle caching, runner/CT520 configuration changes, dependency upgrades, application changes, PR #5 work, or GitHub workflow redesign.
What changed
.forgejo/ci/bookwave-ci/Dockerfile;.forgejo/ci/bookwave-ci/verify.sh;.forgejo/workflows/build-ci-image.yml;scripts/codex/setup.shwithBOOKWAVE_ANDROID_SDK_MODE=preinstalled;verifyDebug;release-checks;apk;docs/release.md.The setup script still validates the environment. In
preinstalledmode it verifies the command-line-tools marker, platform-tools, Android 36 platform and build-tools 36.0.0, and it does not mutate/download Android SDK packages.Published image
Human tag:
forgejo.homebord.org/alexander/bookwave-ci:android36-jdk17-v1Source-SHA tag:
forgejo.homebord.org/alexander/bookwave-ci:sha-65c7928fabadImmutable reference consumed by CI:
forgejo.homebord.org/alexander/bookwave-ci@sha256:bf0f8f06ed41f9dd98b36332b2f1170906d0363c89fdd7c918ce0186844b6b85Image contract verified during publication:
The Android command-line-tools archive and gitleaks archive are SHA-256 pinned.
Registry publication
Forgejo UI run #63 published the image successfully.
The Forgejo runner's internal service URL is HTTP while the canonical registry is
forgejo.homebord.org. Authentication to the canonical registry worked, but a large layer upload through the external reverse-proxy path returned HTTP 502. The repository workflow therefore uploads layers directly to the same Forgejo registry service using the runner-providedFORGEJO_SERVER_URL, then resolves both public tags again throughforgejo.homebord.organd requires them to have the same digest.No CT520, Podman, Proxmox, or insecure-registry configuration was changed.
Exact-head validation
Final branch HEAD:
3dd06e10fc925632b3e3bb08820c17b2aab2140cCurrent base
main:812a936822652e5553c718a488ddab7730cdea2aForgejo UI run #65 ran the strongest manual pull-request gate on that exact final HEAD with
force_rerun=true:verifyDebug --rerun-tasks: 11m16spreinstalledmode.Performance against the post-PR-#52 baseline:
verifyDebug --rerun-tasksThe image removes the repeated Android/JDK/gitleaks bootstrap, but Gradle/dependency work remains the dominant cost. Persistent Gradle caching remains a separate follow-up by design.
APK smoke
Forgejo UI run #66 exercised the protected Android APK path on the same exact final HEAD with
run_checks=false(the full gate had already passed in #65):3dd06e10...;:app:assembleDebugcompleted successfully in 3m02s;0.10.6.1-2066-pr53;org.homebord.bookwave.debug;Follow-up
Persistent Gradle caching is intentionally not part of this PR and is the next CI-performance slice.
No merge requested. The repository owner will review and merge manually.
CI image handoff status:
BOOKWAVE_PACKAGE_TOKENis not configured;Required owner action:
alexanderwith package-registry write permission (minimum practical scope:write:package);BOOKWAVE_PACKAGE_TOKEN;After the secret exists, the same PR will:
forgejo.homebord.org/alexander/bookwave-ci:android36-jdk17-v1;No merge requested.
CI-image slice is complete on exact branch HEAD
3dd06e10fc925632b3e3bb08820c17b2aab2140c.Final evidence:
forgejo.homebord.org/alexander/bookwave-ci:android36-jdk17-v1;sha256:bf0f8f06ed41f9dd98b36332b2f1170906d0363c89fdd7c918ce0186844b6b85;sha-65c7928fabad;verifyDebug --rerun-tasks11m16s, 1184/1184 tasks executed;0.10.6.1-2066-pr53; signer verified against the configured BookWave signing identity;The earlier handoff comment about the missing package token is superseded by this result. No merge performed.