ci: build the deployed images, and deploy the ones CI builds #54
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/ci-build-images"
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?
Summary
cum-tools rebuilt the mcphub images on every deploy.
nix/module.nixbuilt them with the host'spkgs, so the host always asked for its own derivations that no CI ever builds. Now the flake's module deploys the flake's own images, and CI builds exactly those.Importing
nix/module.nixdirectly (the module and VM tests do) works as before.Evidence
nix flake check --no-build: all checks pass.checks.x86_64-linux.*here0yfqakyw…-mcphub.tar.gz,xqny9zds…-mcphub-runner.tar.gzqysdsk98…-mcphub.tar.gz,f38qn1x2…-mcphub-runner.tar.gzqysdsk98…,f38qn1x2…trail checkflags "pure Nix base image" and "building Docker images in CI" as ruled out. Neither applies here: the images keep the pinned Debiannodebase fromnix/images.nix, unchanged, anddockerToolsbuilds them without a container daemon.Merge Danger
Door: two-way
Blast Radius: CI-time
CI now builds both images on every push, which takes longer the first time and is cached in cum-ci's store after that. For hosts that use
nixosModules.defaultwithout a cache, nothing changes: they build the same images, now with mcphub's pinned nixpkgs rather than their own. The follow-up in cumsek/nix dropsinputs.mcphub.inputs.nixpkgs.followsonce this reachesmain.🤖 Generated with Claude Code