In reply to @raitobezarius:matrix.org
Maybe my dumb view on this is I need to get an Ampere Altra Q80-30 somewhere, wire this up to gigabit (or even 100mbps) and then we get faster CI to some extent

fwiw in some of these kooky nix startup companies that i worked with over the years, we started out using self-hosted ci builders (especially for darwin, but also for arm in one case) and it actually worked fine, although of course you gotta be careful about who can trigger it.

I do have one friend over at equinix metal and I don't know if they would help out one day in the future but it's possible.

I am excited about a branch of nix where people are starting to try and fix the issues, document things and evolve ecosystem and core.

In reply to @raitobezarius:matrix.org
More generally how a Nix aware CI component will decide to place a build on a piece of compute (policy, binpacking, etc.)

In reply to @jkachmar:matrix.org
he ended up just ignoring the remote build protocol tho; our system is basically a centralized, work-stealing queue fashioned after the graph of whatever derivations get submitted.

since it's all coordinated w/ Postgres, builders progress thru the graph by querying for available derivations based on builder features, weights, etc.

In reply to @raitobezarius:matrix.org
Maybe my dumb view on this is I need to get an Ampere Altra Q80-30 somewhere, wire this up to gigabit (or even 100mbps) and then we get faster CI to some extent

In reply to @darkkronicle:jpxs.io
(Let me know if I should ask this question somewhere else). Is there a way to debug why Lix is building from source and not using the binary cache? It installs just fine, just wondering if it's on my end. I added the substituter to my substituter list and double checked the public key. (My current version is 2.90.0-beta.1-lixpre20240506-b6799ab). Each time it builds it gives me a different hash, so maybe I have a weird dependency issue?

inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
    lix = {
      url = "git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.1";;
      flake = false;
    };
    lix-module = {
      url = "git+https://git.lix.systems/lix-project/nixos-module";;
      inputs.lix.follows = "lix";
      inputs.nixpkgs.follows = "nixpkgs";
    };
   ...
}

In reply to @puck:puck.moe
The version of Lix in nixpkgs will likely lag behind by a bit; and the dedicated overlay/module will build other packages that depend on Nix with Lix as well; which doesn't happen in nixpkgs.