!zghijEASpYQWYFzriI:nixos.org

Hydra

363 Members
101 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
28 Dec 2025
@k900:0upti.meK900 Hydra is really designed to be post-merge and nixpkgs sized 15:55:58
@k900:0upti.meK900 Your use case is neither 15:56:05
@ungeskriptet:matrix.org@ungeskriptet:matrix.org left the room.16:01:22
@eveeifyeve:matrix.org@eveeifyeve:matrix.orgSo you use build-bot/github actions for that right?16:02:13
@eveeifyeve:matrix.org@eveeifyeve:matrix.org* So you use build-bot/github actions for that right? Because I am not sure to use build-bot along with hydra.16:02:31
@k900:0upti.meK900 I'm not sure who "you" is but generally that's probably what you want yes 16:02:42
@eveeifyeve:matrix.org@eveeifyeve:matrix.org* So you use buildbot/github actions for that right? Because I am not sure to use buildbot along with hydra.16:02:36
@tomberek:matrix.orgtomberek

eveeifyeve: There is a Hydra plugin to make a jobset per PR from Github webhooks. It does work and it is possible to connect it to GHA status reports, but it has pretty minimal usage, poorly documented, and might run into bugs. (i've used it at a small scale)

Another option would be to submit jobs directly using the Hydra API per GitHub Action. Also, this use-case isn't thoroughly developed either.

I do think some kind of easy Hydra / Generic-Forge integration would be nice to have. I see a bunch of places essentially re-inventing this all the time.

18:49:20
@eveeifyeve:matrix.org@eveeifyeve:matrix.orgI might be better off making my own CI.18:50:33

Show newer messages


Back to Room ListRoom Version: 6