Hydra | 374 Members | |
| 109 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Feb 2024 | ||
| but i should try not to stare at it too long and maybe get some sleep. | 07:51:08 | |
could i please ask someone to help me figure out how to use runCommand (or probably better for my case dynamicRunCommand) and nix-support/hydra-build-products to rsync built products and also give me a URL to them? (hacker1024 in case you're around) | 20:46:18 | |
| in particular i just don't have any idea where i'd begin to edit my flake.nix to add a script, and i saw here
which i see is a bash script, so does that sort of thing need to be run by the runCommand? i assume | 20:50:45 | |
| bri: Hydra will detect outputs in those locations and provide helpful links to them. This is purely for Hydra integration. You would have a hydraJob that would reference the specific artifacts you want so that it would generate nice links. So something like:
| 20:56:11 | |
| right now my hydraJobs is ```nix
| 20:59:59 | |
| * right now my hydraJobs is
(snipping out the ones that i commented out), so would i add that as another job and it would get added as another job? or do i put runCommand into the existing job? and where do i stick the actual script for runCommand?
| 21:00:14 | |
| * right now my hydraJobs is
(snipping out the ones that i commented out), so would i add that as another job and it would get added as another job? or do i put runCommand into the existing job? and where do i stick the actual script for runCommand? | 21:00:30 | |
i'm honestly not even sure if this is how i should define my hydraJobs in the first place. i just did myJobName = self.whatever to build the thing that i'd get from nix build ./myFlake#whatever | 21:02:29 | |
* i'm honestly not even sure if this is how i should define my hydraJobs in the first place. i just did myJobName = self.whatever to build the thing that i'd get from nix build ./thisSameFlake#whatever | 21:02:36 | |
| 22 Feb 2024 | ||
| 00:13:34 | ||
| can someone with merge rights review/merge https://github.com/NixOS/hydra/pull/1363 and cherry-pick it to the 2.19 branch we use on hydra.nixos.org? :) | 12:45:13 | |
| 23 Feb 2024 | ||
| 03:28:34 | ||
| Oh yeah probably should post it here too https://github.com/NixOS/hydra/pull/1364 | 15:50:25 | |
| I'm pretty sure I got it right | 15:50:35 | |
| But I don't have a Hydra to test on | 15:50:43 | |
| But I did copy the urlencode incantation | 15:51:01 | |
| * But I did copy the urlencode incantation from another place in Hydra where it presumably works | 15:51:09 | |
| 16:46:46 | ||
| 26 Feb 2024 | ||
| 06:53:11 | ||
I have a hydra server running. It's building packages correctly, and I can reach it. But for some reason I can't verify the signature of the packages on it. I have added the public key to the nix.settings.trusted-public-keys and set nix.extraOptions = "secret-key-files = /path/to/my/secret/key"; Is there a way to manually check the signature on the packages served by hydra? It's using a local store to serve the packages, not a BinaryCacheStore. | 06:59:36 | |
| "nix path-info --json" can show you the signatures. How are you signing the packages right now in Hydra? | 11:32:49 | |
I just set nix.extraOptions = "secret-key-files ...";, which as far as I understood should be what hydra uses when we just the the local store? | 12:07:45 | |
| or am I completely misunderstanding this part? | 12:21:59 | |
| hmmm.. Guess I have missunderstood, as stuff is not signed | 12:23:22 | |
| That would apply only for built paths (not substituted) and local (not remote builders). You may be looking for the hydra store_uri option with a query parameter to specify the key. | 12:33:44 | |
| ack, thanks. I'll look at that | 13:04:03 | |
is it valid to say store_uri = file:///nix/store?secret-key=/my/secret/key? | 13:07:10 | |
| Yes, but if memory serves, you may want "local?secret-key..." so that it talks to the daemon. | 18:04:49 | |
store_uri = "local?secret-key=..." gives me error: don't know how to open Nix store | 18:15:38 | |
should it be localhost, or maybe s3://localhost ? | 18:15:56 | |