| 29 Mar 2026 |
 John Ericson | To be clear, that PR should definitely go to staging first, and should not hold up the deployment to prod | 15:59:22 |
| John Ericson | the other changes I have read at code review time quite closely, and I would not be so concerned | 16:00:10 |
| John Ericson | I definitely agree we don't want a buch more dev to pile up and then we end up with something that cannot be deployed | 16:01:01 |
| 30 Mar 2026 |
 Janne | Only the AI overlords can tell by now | 13:25:05 |
| 6 Apr 2026 |
|  whispers [& it/fae] joined the room. | 05:55:06 |
|  Hythera joined the room. | 21:49:44 |
| 7 Apr 2026 |
|  Proesmans Bert joined the room. | 18:48:23 |
| 8 Apr 2026 |
 Mic92 | Hands up who is using Hydra with non-git / non-flake inputs especially VCS like mercurial/darcs/svn. | 09:21:53 |
| Mic92 | I am thinking that we might want to reduce the feature scope of hydra a bit. | 09:22:10 |
| Mic92 | * Hands up who is using Hydra with non-git / non-flake inputs especially version control systems like mercurial/darcs/svn. | 09:22:24 |
| Janne | Throw out the channels as well while you're at it | 14:21:42 |
 Sandro | I have overwritten them them with null since forever 😂 | 14:25:18 |
 hacker1024 | We're using text, Nix expression, Boolean inputs etc. to configure certain jobsets | 14:26:50 |
| John Ericson | Simon Hauser: does long term more harmonia for local store and/or hydra database for derivations sound acceptible for you in place of more ffi for now? | 15:08:46 |
| John Ericson | Simon Hauser: I am redoing it with aterm and the physical path | 15:53:44 |
| John Ericson | hexa: FYI the darwin builder builds are enabled | 17:52:47 |
| John Ericson | https://hydra.nixos.org/eval/1824313#tabs-unfinished I just bumped up in the queue | 17:52:58 |
| John Ericson | so we could finish the staging hydra builders deploy | 17:53:08 |
| John Ericson | (maybe this was better for #infra:nixos.org ) | 17:53:40 |
| John Ericson | BMG: it might be good to collaborate on the feasiblity of some migrations? | 18:25:48 |
| John Ericson | for example "do the root build and root build step, once there exists a ltter which is done, always agree on output info"? | 18:26:19 |
 BMG | I should be able to set aside some time this month | 18:50:12 |
| BMG | Later in the month | 18:50:29 |
| John Ericson | Sounds good! | 18:50:44 |
 hexa | do you mean the version mismatch is resolved? | 23:03:24 |
| 9 Apr 2026 |
 Sapii | Hydra is taking its sweet time testing the nix patch for nixos-unstable ðŸ˜ðŸ˜ | 00:49:42 |
| Sapii | * Hydra is taking its sweet time testing the nix patch for nixos-unstable ðŸ˜ðŸ˜ ( been the entire day ) | 00:49:56 |
| Sapii | A more technical question, is it possible for hydra to pause jobsets and differentiate between commits as to pause a jobset and prioritize building a certain commit? If not, would it be beneficial to add this for future "CVE events"? I am interested in contribuiting to something like this ( as well as learning about hydra internals ) | 01:20:42 |
 Sergei Zimmerman (xokdvium) | In reply to @opandddd:matrix.org
A more technical question, is it possible for hydra to pause jobsets and differentiate between commits as to pause a jobset and prioritize building a certain commit? If not, would it be beneficial to add this for future "CVE events"? I am interested in contribuiting to something like this ( as well as learning about hydra internals ) Hydra already has a way to bump jobs to the front of the queue. When building nix releases (esp security) we do that | 01:23:51 |
| Sapii | Nice, and I am assuming this bump was used for this patch too? | 01:32:17 |
