logoalt Hacker News

steeleduncanyesterday at 3:49 PM4 repliesview on HN

I do the same with Nix as it works for macOS builds as well

It has the massive benefit of solving the lock-in problem. Your workflow is generally very short so it is easy to move to an alternative CI if (for example) Github were to jack up their prices for self hosted runners...

That said, when using it in this way I personally love Github actions


Replies

0x457yesterday at 8:11 PM

Nix is so nice that you can put almost your entire workflow into a check or package. Like your code-coverage report step(s) become a package that you build (I'm not brave enough to do this)

I run my own jenkins for personal stuff on top of nixos, all jobs run inside devenv shell, devenv handles whatever background services required (i.e. database), /nix/store is shared between workers + attic cache in local network.

Oh, and there is also nixosModule that is tested in the VM that also smoke tests the service.

First build might take some time, but all future jobs run fast. The same can be done on GHA, but on github-hosted runners you can't get shared /nix/store.

malikeryesterday at 4:11 PM

I'm scared by all these references to nix in the replies here. Sounds like I'm going to have learn nix. Sounds hard.

show 1 reply
dfeeyesterday at 9:41 PM

same here. though, i think bazel is better for DAGs. i wish i could use it for my personal project (in conjunction with, and bootstrapped with nix), but that's a pretty serious tooling investment that I just feel is just going to be a rabbit hole.

wredcollyesterday at 4:38 PM

Whata the killer benefit of nix over, like, a docker file or a package.lock or whatever?

show 1 reply