circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#608 The Linux desktop jobs run in a prebuilt desktop build image (#605)

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#608
  • pull request
  • state:merged

Part of #605: its second image. The Linux desktop jobs run in a prebuilt image instead of installing a dozen packages, Rust and `tauri-driver` on every run. The image also lets a machine without WebKitGTK build and test the desktop app. ## The image - **Dockerfile:** `deploy/desktop-build/Dockerfile`. - **Base:** Ubuntu 24.04, pinned by digest, as the runners use. - **Packages:** - the desktop build's and the desktop UI test's packages: WebKitGTK, GTK, the Tauri libraries, GMP, SQLite, WebKitWebDriver and Xvfb; - what GitHub's runner image otherwise provides them: git, file, xz, xauth and libssl. - **Toolchains:** Node.js 24.21.0 with its checksum checked, Rust 1.99.0 with rustfmt, and `tauri-driver` 2.1.0, which the UI test otherwise compiles on every run. - **Publishing:** `scripts/build-images.mjs` builds it, tagged with a hash of the Dockerfile. `build-images.yml` publishes it to `ghcr.io/openchronology/desktop-build` and attests it. ## In CI - **Finding the image:** a small job in `desktop.yml`, and another in `ci.yml`, run `node scripts/build-images.mjs --find desktop-build`. It gives the published image pinned by digest, or nothing. - **With it:** `linux-deb`, `linux-appimage` and `desktop-ui` run in it and skip their apt steps. `desktop-ui` also skips installing `tauri-driver`. - **Without it:** an empty image runs no container. The jobs run on the runner and install their packages as before. The macOS and Windows targets always get an empty image. - **Permissions:** `ci.yml` and `release.yml` give these jobs `packages: read`. ## Tested locally I built the image here (3.5 minutes, 2.8 GB) and ran each job's steps in it in a clean worktree: - **The desktop packages job:** `npm ci`, `build:editor`, `cargo fmt --check`, and the `native-store` and `src-tauri` tests all pass. `src-tauri` hadn't compiled on this machine before; its 17 tests pass. - **Packages:** `scripts/desktop/build.mjs linux-deb` and `linux-appimage` built `openchronology-desktop-linux-amd64.deb` (11 MB) and the AppImage (90 MB). - **The desktop UI test's path:** `tauri build --debug --no-bundle`, then `test/desktop-access.mjs` and `test/desktop-bulk.mjs` under `xvfb-run` with `tauri-driver`. Both pass. ## Tests - **`test/build-images.test.mjs`:** the image's tag is a hash of its Dockerfile, and the jobs use the image only when it's found. - **`test/ci-workflows.test.mjs`:** the image's Node.js matches the server packages'. Its apt and curl retries and its pinned base image are checked like the other Dockerfiles. This PR's first CI run has no published image, so it checks the fallback, including that an empty image runs no container on macOS and Windows. I'll then publish the image from this branch and rerun, to check the jobs inside it before merging. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/circagraph/timeline-app/pull/608

Related

Open #608 The Linux desktop jobs run in a prebuilt desktop build image (#605) in the timeline

#608 The Linux desktop jobs run in a prebuilt desktop…