I just want to share my buildbot configuration setup that I created for nix.
- It uses nix-eval-jobs to evaluate attributes from a flake.nix in parallel.
- It then creates for each attribute its own pipeline step and executes those steps in parallel each with their own build log
- Additionally I added cachix upload support and also a flake update pipeline that merges automatically if the build succeeds.
It turns out while buildbot’s configuration and API is a bit harder to grasp, it’s very dynamic and flexible. And I was able to perfectly fit in nix
into it. While many CIs have their configuration in the source repo these days, for a public nix CI setup, it’s actually beneficial to not allow users to modify the CI code. Instead they can only submit nix code and not access other secrets.
Unlike hydra, pull-request based workflows and integration into github/gitlab etc is much better with proper status updates for failed and succeeded builds.