ci(publish-binary): build binary in Docker via export stage, not on runner #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/remove-container-from-ci"
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?
The first revision of this branch built the binary on the runner with
cargo build --release --locked, which bypassed the rust-builder-musl toolchain pinned in oci-build/Dockerfile and produced a glibc-linked binary tied to the runner's userspace. Switch back to a Docker build that targets the existingexportstage and extracts the artifact via--output type=local,dest=./output. The result is byte-identical in shape to what the previous OCI workflow exported: a musl-static youtrack-cli-linux-x86_64. The image push, runtime stage, registry login, and registry-backed buildcache are intentionally still gone since the runtime image is not a deliverable for a CLI tool. Reintroduce a registry buildcache later only if CI build time becomes a real bottleneck.