.hearthforge-ci.toml
⎇
Raw
1# Steps run in file order, in one container, sharing /ci/build.
2# Alpine, so the published binary is the same static musl build the
3# Containerfile ships.
4
5image = "docker.io/rust:1.90-alpine3.22"
6work_dir = "/ci/build"
7clone_project_to = "/ci/build/project"
8
9# busybox ash, which does support `set -o pipefail`.
10shell = ["/bin/sh", "-c"]
11
12# CARGO_TARGET_DIR must stay outside clone_project_to: the checkout is
13# extracted over that directory, so a cache inside it would be overwritten.
14shell_setup = """
15set -euo pipefail
16export CARGO_TARGET_DIR=/ci/cache/target
17"""
18
19timeout = 5400
20memory_limit = "6g"
21
22# Caps are a safety valve against unbounded growth, not a budget: hitting one
23# costs a full rebuild. Sized roughly twice the working set. A local target
24# holding all three profiles measures 26G, of which debug is 22G.
25cache = [
26 { path = "/ci/cache/target", max_size = "20g" },
27 { path = "/usr/local/cargo/registry", max_size = "4g" },
28 { path = "/root/.bun/install/cache", max_size = "2g" },
29]
30
31[on]
32push = ["master"]
33tag = true
34
35# bun publishes no musl installer, so take the binary from the official image.
36# This mirrors the Containerfile's COPY --from. The -alpine tag is required:
37# the glibc build will not run here. bun also needs libstdc++, which setup
38# installs before anything executes it.
39[[copy]]
40image = "docker.io/oven/bun:1.4.0-alpine"
41from = "/usr/local/bin/bun"
42to = "/usr/local/bin"
43
44[variables]
45
46 [variables.TRUNK_VERSION]
47 default = "0.21.14"
48 description = "Trunk release that builds the wasm frontend. Matches the Containerfile."
49
50# ── toolchain ────────────────────────────────────────────────────────────────
51# binaryen supplies wasm-opt. Without it trunk downloads a glibc build that
52# cannot run on musl. just comes from apk here, so no install script.
53[[steps]]
54name = "setup"
55timeout = 900
56run_sh = """
57# openssl-dev + openssl-libs-static: webauthn-rs links OpenSSL, and this is
58# a static musl build. Mirrors the Containerfile's build stage.
59apk add --no-cache musl-dev binaryen just curl libstdc++ podman-remote \
60 openssl-dev openssl-libs-static pkgconfig
61
62# The official rust images use rustup's minimal profile, so rustfmt and
63# clippy are absent. `just lint` needs both.
64rustup component add rustfmt clippy
65rustup target add wasm32-unknown-unknown
66
67url="https://github.com/trunk-rs/trunk/releases/download/v${TRUNK_VERSION}/trunk-x86_64-unknown-linux-musl.tar.gz"
68curl -fsSL -o /tmp/trunk.tar.gz "$url"
69curl -fsSL "$url.sha256" | awk '{print $1 " /tmp/trunk.tar.gz"}' | sha256sum -c -
70tar xzf /tmp/trunk.tar.gz -C /usr/local/bin
71rm -f /tmp/trunk.tar.gz
72
73just --version && bun --version && trunk --version
74cargo fmt --version && cargo clippy --version
75"""
76
77# ── checks ───────────────────────────────────────────────────────────────────
78# Formatting and clippy findings are reported, not gated. The CI toolchain is
79# 1.90 and local machines run newer, so clippy disagrees across versions.
80[[steps]]
81name = "lint"
82run_sh = "cd project && just lint"
83warn_on_fail = true
84
85# `just test` covers server and api-types only, hence the extra web run.
86[[steps]]
87name = "test"
88run_sh = "cd project && just test && cargo test -p web"
89
90# ── build ────────────────────────────────────────────────────────────────────
91[[steps]]
92name = "build"
93timeout = 2400
94run_sh = "cd project && just build"
95publish_file = ["/ci/cache/target/release/filebrowser-ng"]
96
97# `just e2e` would rebuild the frontend. The build step already staged
98# server/dist, so run the embedded suite against it directly.
99[[steps]]
100name = "e2e"
101run_sh = "cd project && cargo test -p server --features embedded"
102
103# ── release ──────────────────────────────────────────────────────────────────
104[[steps]]
105name = "release"
106run_if = 'test -n "${CI_COMMIT_TAG}"'
107run_sh = """
108cd project
109install -Dm755 "${CARGO_TARGET_DIR}/release/filebrowser-ng" \
110 "dist/filebrowser-ng-${CI_COMMIT_TAG}-x86_64-linux-musl"
111"""
112publish_gzip = ["/ci/build/project/dist/"]
113
114# ── image ────────────────────────────────────────────────────────────────────
115# Packages the binary the build step made, so the image ships exactly what
116# e2e tested. The Containerfile's build stage is skipped via BIN_STAGE.
117# engine_socket hands this step the host engine, which is Podman on this
118# server (needs CI_ENGINE_SOCKET=1). REGISTRY_PASSWORD is a CI secret with the
119# admin password. CI_REGISTRY is "<host>/<repo>" on the built-in registry.
120# Tags: every run pushes the short sha and "edge"; a tag run also pushes the
121# tag and "latest".
122[[steps]]
123name = "image"
124engine_socket = true
125timeout = 900
126run_sh = """
127cd project
128mkdir -p ci-bin
129cp "${CARGO_TARGET_DIR}/release/filebrowser-ng" ci-bin/filebrowser-ng
130
131echo "$REGISTRY_PASSWORD" | podman-remote login "${CI_REGISTRY%%/*}" -u admin --password-stdin
132
133# A remote build sends a seccomp profile path that the server opens. Alpine
134# ships one at /etc/containers/seccomp.json and podman picks it over the
135# /usr/share copy, but the server has only the latter. Ask the server for its
136# own path. An empty answer means no profile can be named, so the build runs
137# unconfined rather than failing.
138prof=$(podman-remote info --format '{{.Host.Security.SECCOMPProfilePath}}' 2>/dev/null || true)
139if [ -n "$prof" ]; then
140 seccomp="seccomp=$prof"
141else
142 seccomp="seccomp=unconfined"
143fi
144
145img="$CI_REGISTRY:$CI_COMMIT_SHORT_SHA"
146podman-remote build --security-opt "$seccomp" \
147 -f Containerfile -t "$img" --build-arg BIN_STAGE=prebuilt .
148podman-remote push "$img"
149
150if [ -n "${CI_COMMIT_TAG:-}" ]; then
151 tags="$CI_COMMIT_TAG latest"
152else
153 tags="edge"
154fi
155for t in $tags; do
156 podman-remote tag "$img" "$CI_REGISTRY:$t"
157 podman-remote push "$CI_REGISTRY:$t"
158done
159"""
160