| 16 May 2026 |
 tomberek | I'm keen to try things out... but only been lurking as I'm not quite sure when/if it is in a good state to test (mainly interested in a centralized scheduler with a de-centralized/binary-cache store as the source of truth). What would be helpful here? Docs? Users playing with it? Code? Review? | 20:28:55 |
| 17 May 2026 |
 Mic92 | tomberek: users playing with would be good | 04:55:44 |
| Mic92 | in theory could you not have the queue-builder running on your hydra as well and use nix remote build protocol? Also this sounds a bit like an insane setup. | 04:56:37 |
| Mic92 | https://github.com/NixOS/hydra/pull/1747 <- Ever since I saw this code the interpolation for flakes scared me. | 04:57:05 |
| Mic92 | Simon Hauser: Janne I would like to merge the ofborg infra into the nixos infra repo: https://github.com/NixOS/infra/pull/1009
reason is that this makes it easier to keep staging hydra in sync with the ofborg builder's queue-builder agent. Also shipping security updates on a more regular base is easier this way. I think you should still be able to deploy machines. Potentially we could also give our merge access to the infra repo? | 05:50:47 |
| Mic92 | Janne: in case simon, doesn't read my message, please let him know about the pull request | 05:51:18 |
 hexa | sgtm | 12:13:36 |
| 18 May 2026 |
 Janne | I tried to keep it similar to make such a migration easier in the future. So I am fully on board with that. The merge access is something that may be helpful and I would take it if given to me but it's not something I will explicitly require or that I think is strictly necessary | 16:42:46 |
| hexa | merge access is complicated without joining infra, because it is not in a dedicated subtree | 19:04:14 |
| hexa | though you'd be welcome to join | 19:04:37 |
| 19 May 2026 |
|  amadaluzia changed their profile picture. | 20:59:04 |
| 21 May 2026 |
 Sergei Zimmerman (xokdvium) | What’s the overall plan to continue maintaining HNO deployment? For now infra pins a specific commit, but it would be valuable to have a branch where additional fixes can be applied while the new queue runner is not in a good state. | 12:15:36 |
 vcunat | I'm not sure why it pins the commit, but it's exactly on the tip of the infra branch. | 12:18:19 |
| vcunat | * I'm not sure why it pins the commit, but it's exactly on the tip of the infra branch currently. | 12:18:36 |
| Sergei Zimmerman (xokdvium) | Ah ok | 12:19:35 |
| hexa | huh? it is what? | 13:29:15 |
| hexa | hydra = {
url = "github:NixOS/hydra/a40d42862da88cce78a27dd594e1484a034aac4d";
inputs.nixpkgs.follows = "nixpkgs";
inputs.nix.follows = "nix";
};
| 13:29:41 |
| vcunat | The infra branch points to a40d42862da88cce78a27dd594e1484a034aac4d right now. | 13:30:16 |
| hexa | sorry, but what infra branch where? | 13:30:37 |
| hexa | oh, in hydra | 13:30:49 |
| vcunat | github:NixOS/hydra/infra | 13:30:52 |
| vcunat | Sounds better to me to have this in there (and relock), but that's just a nit. | 13:31:21 |
| hexa | that was created very recently | 13:31:27 |
| hexa | 3 days ago in fact | 13:31:44 |
| hexa | I'd prefer naming this legacy-queue-runner or sth | 13:32:10 |
| hexa | better describes the purpose | 13:32:32 |
| vcunat | I thought the purpose is to have a branch which shows what's running on hydra.nixos.org | 13:32:54 |
| vcunat | * I thought the purpose of infra is to have a branch which shows what's running on hydra.nixos.org | 13:33:01 |
| vcunat | * I thought the purpose of NixOS/hydra/infra is to have a branch which shows what's running on hydra.nixos.org | 13:33:13 |
| vcunat | * I thought the purpose of NixOS/hydra/infra is to have a branch which shows what's running on hydra.nixos.org right now | 13:33:22 |
