| 18 Nov 2023 |
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 (Mindavi) | 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 (Mindavi) | The UI doesn't expose it, presumably because it's a very expensive operation on bigger instances | 10:56:08 |