| 24 Aug 2021 |
 @grahamc:nixos.org | anyone have opinions on this PR adding a prometheus exporter? | 15:13:52 |
| @grahamc:nixos.org | oops, this one: https://github.com/NixOS/hydra/pull/1001 | 15:14:25 |
 andi- | this PR? | 15:14:28 |
| andi- | ah | 15:14:29 |
| andi- | Probably unrelated to this PR but shouldn't we have Nix options to define all these things? Having to go back to (templated) strings feels pretty counterintuitive. | 15:15:51 |
| andi- | Also they are basically not discoverable unless you read the Hydra source (and some of the docs). | 15:16:18 |
| @grahamc:nixos.org | Good question, I, uh -- maybe? | 15:17:16 |
| @grahamc:nixos.org | I should probably put this in the PR template but I'm really looking for patches that is adjacent to / changes config to include docs at a minimum, should it also include module updates? perhaps | 15:18:36 |
| andi- | I guess for now it is fine to carry on with the status quo. As soon as some (poor) soul has put in the time to create options for everything (we know of) that changes. | 15:20:36 |
| andi- | I left a few comments on the PR. I really don't like the mmap JSON thingy that you explained there. If you wouldn't have explained it I might not have bothered. | 15:24:11 |
| @grahamc:nixos.org | yeah, I explained it because I really don't like it and would like it if someone had a better idea :) | 15:25:59 |
| @grahamc:nixos.org | replied :) | 15:33:42 |
| @grahamc:nixos.org | andi-: did you have any follow-up thoughts w.r.t. the text file exporter? | 18:09:36 |
| andi- | I haven't looked again | 18:43:56 |
|  adisbladis joined the room. | 18:48:42 |
| @grahamc:nixos.org | fair enough :) | 19:07:29 |
| 25 Aug 2021 |
 ma27 | grahamc (he/him): do you have an idea what's going on with https://hydra.nixos.org/jobset/nixpkgs/glibc-2.34#tabs-errors ? :) | 10:39:44 |
| ma27 | (it only says evaluation failed with exit code 255) | 10:39:53 |
| andi- | How hard is it to add jobset ownership to hydra? It already supports that to some degree but IIRC you can't assign jobsets to users once they are created? | 14:07:10 |
| @grahamc:nixos.org | hmm.. do jobsets have owners? | 14:08:00 |
| andi- | I've seen it in the permissions checks IIRC | 14:08:56 |
| andi- | That might have been per project. | 14:09:25 |
| andi- | I was just thinking of e.g. the haskell folks should be owner of the haskell-updates jobset etc.. So that we offload some of the admin work that is occasionally requested. | 14:10:27 |
| andi- | It would still be only one person but that would already add another dimension of offloading. | 14:10:48 |
| andi- | I can see that this might be an issue as for example the scheduling shares are managed within a jobset and not from the "outside". | 14:12:03 |
 sterni | I agree that that is not ideal, but tbh even with a jobset's internal configuration you'd be able to exact some kind of abuse, so owners would need to be trustworthy regardless | 14:13:35 |
| andi- | Yeah. I am more thinking in line of "I need to be able to restart / cancel / ... a job" within a specific jobset without having to hand out global permissions like we do right now.l | 14:14:13 |
| andi- | It isn't an issue but I think it would bel nice to be able to provide more access to hydra to trusted contributors with the ability to keep the scope smaller. | 14:14:51 |
| sterni | probably we'd need to implement an ACL system at some point which allows to give out permissions per jobset | 14:15:51 |
| sterni | maybe even per job, so maintainers can restart “their” jobs if they are flaky | 14:16:06 |
