| 4 Nov 2021 |
 Mic92 | Why is the prometheus endpoint per job and not per jobset? | 18:36:55 |
| Mic92 | Nevermind. I can just use telegraf's sql input for that. | 18:45:20 |
 @grahamc:nixos.org | what would you like it to say per jobset? | 18:56:55 |
| @grahamc:nixos.org | one reason I didn't make it per jobset is indeed I wanted to monitor a specific job | 18:57:13 |
| @grahamc:nixos.org | so, probably the reason is nobody built it yet :P | 18:57:23 |
| Mic92 | grahamc: getting an alert if one of my build fails: https://hydra.thalheim.io/eval/160 | 18:58:45 |
| @grahamc:nixos.org | gotcha, so just monitor the entire jobset instead of an aggregate job | 18:59:13 |
| @grahamc:nixos.org | makes good sense to me | 18:59:16 |
| Mic92 | @grahamc: only issue is if you use this endpoint on nixpkgs with 100.000 jobs per jobset. | 19:00:04 |
| @grahamc:nixos.org | yeah, that is also why I haven't tried to implement it :) | 19:00:30 |
| @grahamc:nixos.org | there is a gulf between "Most users" and "hydra.nixos.org" on appropriate features | 19:00:55 |
 das_j | sounds like return if Sys::Hostname == "NAME_OF_THE_NIXOS_HOST" | 19:01:42 |
| @grahamc:nixos.org | puke | 19:01:52 |
| das_j | * sounds like return if Sys::Hostname::hostname == "NAME_OF_THE_NIXOS_HOST" | 19:01:53 |
| @grahamc:nixos.org | I mean, finding ways to make the queries efficient would be cool | 19:02:21 |
| Mic92 | @cole-h: can I use type == "githubpulls" with this flake-enabled repos? https://github.com/DeterminateSystems/terraform-provider-hydra/blob/49a6e07486ce42894b859ebc44cb6dbf36d07902/examples/default/main.tf#L61 | 19:28:08 |
 cole-h | IIRC githubpulls is a legacy input type, so I don't think so... | 19:54:10 |
| cole-h | Can you do that if you create it from the Hydra web UI? | 19:54:25 |
| Mic92 | cole-h: you are right. That's not a thing. That's a weird limitation. | 19:59:54 |
| @grahamc:nixos.org | ma27 has a PR which makes it possible to add inputs to a flake. I was hesitant because I think the UI is destined to be confusing, but that hasn't stopped much in Hydra before :P | 20:32:36 |
 ma27 | I added a big warning above the form if flakes are supposed to be used. So it's ugly, but the behavior shouldn't be too unexpected :)
using this patch for a few months btw and it seems to work fine for me :) | 20:43:22 |
| Mic92 | well. I think I can live with the current approach: https://github.com/Mic92/dotfiles/blob/master/nixos/eve/modules/hydra/jobs.tf | 20:44:38 |
| ma27 | yup, that's what I planned to do in my setup at some point anyway, but I still think it makes sense to support that in the UI as well %) | 20:49:31 |
| Mic92 | wow, the github pr integration is super hacky: https://github.com/cleverca22/hydra-configs/blob/eae3caea99ca01af1b9641e375112f0036a30e70/not-os/default.nix#L44 | 21:56:26 |
 cleverca22 | yep | 21:56:55 |
| cleverca22 | hydra has a special input type, that will fetch the pull list and pass it to you as json | 21:57:07 |
| cleverca22 | your nix code is then responsible for incorporating that into the declarative jobsets | 21:57:28 |
| Mic92 | ma27: Would this PR enable github pull request with flakes? https://github.com/NixOS/hydra/pull/922/files I mean I would the same json file that one cannot use it in flakes. | 22:09:03 |
| ma27 | it works fine for gitea status, IIRC the github pr plugin uses a similar mechanism, so most likely yes :) | 22:11:10 |
| Mic92 | the github pullrequest plugin generates a file like this: https://github.com/cleverca22/hydra-configs/blob/eae3caea99ca01af1b9641e375112f0036a30e70/sample-pr.json | 22:13:45 |
