| 15 Nov 2023 |
| @eisfunke:eisfunke.com changed their profile picture. | 22:42:14 |
| 17 Nov 2023 |
| @yuri:nekover.se changed their display name from yuri to fi (she/her). | 01:44:16 |
Arian | Are there docs for Hydra anywhere ? | 13:10:57 |
Arian | https://nixos.org/hydra/manual/ just downloads a partial corrupted html file | 13:11:06 |
Julien | Code source is the documentation right ? | 13:17:03 |
Julien | That being said the link you just sent works for me | 13:17:30 |
Julien | It redirects to https://hydra.nixos.org/build/196107287/download/1/hydra/introduction.html | 13:17:36 |
Arian | which on safari just causes a download due to lacking Content-Typehe ader | 13:18:04 |
Arian | also for me the CSS is broken | 13:18:11 |
Julien | On what ? :p | 13:18:29 |
Arian | on chromium the CSS is broken | 13:18:38 |
Arian |  Download image.png | 13:18:58 |
Julien | Strange | 13:22:38 |
raitobezarius | yep can confirm I have the same issue | 15:50:58 |
@janne.hess:helsinki-systems.de | https://github.com/NixOS/hydra/issues/1267 | 21:15:20 |
| 18 Nov 2023 |
| ElvishJerricco joined the room. | 21:45:22 |
ElvishJerricco | is there any way to have hydra track the merge of two branches? i.e. I want a jobset where the nixpkgs input is the merge of nixos-unstable and a PR I'm interested in. | 21:45:56 |
Julien | I don’t think so, you can create a jobset for that specific branch and rebase it on nixos-unstable, but I’m not sure you can do better | 21:49:51 |
Julien | * I don’t think so, you can create a jobset for that specific branch and rebase it regularly on nixos-unstable, but I’m not sure you can do better | 21:50:23 |
ElvishJerricco | bummer | 21:50:32 |
ElvishJerricco | yea I can run a service on a timer that does that. | 21:50:48 |
| 19 Nov 2023 |
ElvishJerricco | hm, well I did something a little wrong | 01:58:21 |
ElvishJerricco | How do I delete a jobset? It's not obvious to me in the interface | 01:58:29 |
raitobezarius | I don't think you can delete jobsets in Hydra | 02:05:21 |
ElvishJerricco | oof | 02:16:20 |
| pbsds changed their display name from pbsds to pbsds (federation borken, may not see reply). | 03:35:20 |
vcunat | In reply to @marius851000:mariusdavid.fr Hello. I set up an Hydra server for doing some custom CI of a package manager (portmod), and I had a wrongly written fetch script for a fixed output derivation. I now fixed it, but Hydra doesn’t re-evaluate it (certainly cause the result set end up having the same hash). Is there some way I can force it to rebuild all failed derivation according to a new definition even if the result set hash is identical?
(I already had this problem once, and it seems changing the hash of the dependant and re-evaluating wasn’t enought, but I had to change the name anyway, which resulted in a different hash and so a rebuild for every sources) I'm late but yes, that's an issue. I know nothing better than changing the derivation somehow - in a way that changes the output path, so e.g. the name of the fixed-output derivation. | 08:15:29 |
vcunat | Or you could like create a different jobset that contains the corrected derivation - that way you get a new job even if the output path is exactly the same. | 08:16:43 |
@rick:matrix.ciphernetics.nl | In reply to @raitobezarius:matrix.org I don't think you can delete jobsets in Hydra Open a javascript console while logged in and run deleteJobset or sth like that while on the jobset page | 10:55:20 |
@rick:matrix.ciphernetics.nl | The UI doesn't expose it, presumably because it's a very expensive operation on bigger instances | 10:56:08 |