| 26 Sep 2024 |
|  Fabián Heredia set a profile picture. | 01:16:06 |
| 27 Sep 2024 |
|  SigmaSquadron joined the room. | 00:18:20 |
 @asymmetric:matrix.dapp.org.uk | re: this: https://github.com/NixOS/hydra/blob/95003f2eb503f71979856470c7caea946f1ae7f0/doc/manual/src/notifications.md
is this hydra-notify component deployed on prod hydra? are any plugins enabled? i tried looking here for hints, it seems it is deployed but
a) idk if hydra-dev is actually prod
b) whether any plugins are configured
c) whether there's any interest on the infra people's side to deploy one for build notifications
| 08:43:42 |
 K900 | It's deployed but turned off | 08:44:00 |
| K900 | And the reason it's turned off is because it takes up stupid amounts of RAM and no one has figured out why | 08:44:14 |
| K900 | (or as far as I can tell attempted to) | 08:44:18 |
| K900 | And that machine is already severely RAM starved | 08:44:45 |
| K900 | Because it is running nixpkgs evals | 08:44:50 |
 vcunat | The other reason is that we're not aware of any use for it at hydra.nixos.org | 09:16:32 |
| K900 | Honestly I don't think anyone would have cared about it | 09:17:22 |
| K900 | If it didn't use half the RAM on the box | 09:17:26 |
| @asymmetric:matrix.dapp.org.uk | In reply to @vcunat:matrix.org
The other reason is that we're not aware of any use for it at hydra.nixos.org wouldn't it be useful for notifying maintainers of build failures, with mechanisms other than email? | 13:13:35 |
| vcunat | Probably. But I believe there's no code for that. Even this code was unreliable, sending mass notifications in some edge cases IIRC. | 13:46:04 |
 Sandro | IIRC in the last corner of my brain I also saved that those mails where put into the spam directory | 14:44:32 |
| @asymmetric:matrix.dapp.org.uk | is a URL like this one supposed to take me to the last successful build, or the latest build? | 14:48:55 |
| @asymmetric:matrix.dapp.org.uk | looking at e.g. https://hydra.nixos.org/job/nixpkgs/trunk/rippled.x86_64-linux/:
/latest takes me to https://hydra.nixos.org/build/259389382- but the actual latest build is https://hydra.nixos.org/build/271754130
| 14:50:03 |
|  @austreelis:the-apothecary.club left the room. | 16:09:06 |
|  elikoga set a profile picture. | 16:27:32 |
| @asymmetric:matrix.dapp.org.uk | btw i think the something equivalent to the job endpoint does exist:
curl -s -L -H 'Accept: application/json' "https://hydra.nixos.org/api/latestbuilds?nr=1&project=nixpkgs&jobset=trunk&job=taler-merchant.x86_64-linux"
contrary to what the docs say, there does seem to be a whole api endpoint at a separate url than the webpage (see above)
| 20:04:00 |
| @asymmetric:matrix.dapp.org.uk | * btw i think that something functionally equivalent to a job endpoint does exist:
curl -s -L -H 'Accept: application/json' "https://hydra.nixos.org/api/latestbuilds?nr=1&project=nixpkgs&jobset=trunk&job=taler-merchant.x86_64-linux"
contrary to what the docs say, there does seem to be a whole api endpoint at a separate url than the webpage (see above)
| 20:04:14 |
| @asymmetric:matrix.dapp.org.uk | * btw i think that something functionally equivalent to a job endpoint does exist:
❯ curl -s -L -H 'Accept: application/json' "https://hydra.nixos.org/api/latestbuilds?nr=1&project=nixpkgs&jobset=trunk&job=taler-merchant.x86_64-linux"
[{"timestamp":1726685143,"id":272888968,"nixname":"taler-merchant-0.13.0","buildstatus":0,"job":"taler-merchant.x86_64-linux","project":"nixpkgs","finished":1,"system":"x86_64-linux","jobset":"trunk"}]⏎
contrary to what the docs say, there does seem to be a whole api endpoint at a separate url than the webpage (see above)
| 20:04:28 |
| @asymmetric:matrix.dapp.org.uk | * btw i think that something functionally equivalent to a job endpoint does exist:
❯ curl -s "https://hydra.nixos.org/api/latestbuilds?nr=1&project=nixpkgs&jobset=trunk&job=taler-merchant.x86_64-linux"
[{"timestamp":1726685143,"id":272888968,"nixname":"taler-merchant-0.13.0","buildstatus":0,"job":"taler-merchant.x86_64-linux","project":"nixpkgs","finished":1,"system":"x86_64-linux","jobset":"trunk"}]⏎
contrary to what the docs say, there does seem to be a whole api endpoint at a separate url than the webpage (see above)
| 20:07:57 |
| 28 Sep 2024 |
|  @belak:matrix.org joined the room. | 06:03:22 |
| @asymmetric:matrix.dapp.org.uk | In reply to @asymmetric:matrix.dapp.org.uk
btw i think that something functionally equivalent to a job endpoint does exist:
❯ curl -s "https://hydra.nixos.org/api/latestbuilds?nr=1&project=nixpkgs&jobset=trunk&job=taler-merchant.x86_64-linux"
[{"timestamp":1726685143,"id":272888968,"nixname":"taler-merchant-0.13.0","buildstatus":0,"job":"taler-merchant.x86_64-linux","project":"nixpkgs","finished":1,"system":"x86_64-linux","jobset":"trunk"}]⏎
contrary to what the docs say, there does seem to be a whole api endpoint at a separate url than the webpage (see above)
i guess what i'm asking is, can i rely on this endpoint sticking around, or is it part of some private/unstable API that will be removed? | 10:43:40 |
| @belak:matrix.org | Are there any good tutorials for using Hydra? I've been debating between Hydra and Woodpecker for personal CI and figured I'd use hydra but most of the docs I've seen so far are just how to enable the service and get an admin set up - nothing about projects or jobsets or how to actually configure it. | 15:02:20 |
| K900 | Don't | 15:02:28 |
| K900 | Hydra is a NixOS sized solution for a NixOS sized problem | 15:02:36 |
| K900 | It's not a good fit for personal CI | 15:02:45 |
| @belak:matrix.org | Fair enough | 15:04:53 |
 hacker1024 | Eh, with declarative jobsets it's not too bad once you get over the learning curve. It has a built in binary cache server and everything | 15:05:43 |
