!zghijEASpYQWYFzriI:nixos.org

Hydra

374 Members
109 Servers

Load older messages


SenderMessageTime
18 Feb 2024
@bri:catgirl.cloudbribut i should try not to stare at it too long and maybe get some sleep.07:51:08
@bri:catgirl.cloudbri 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
@bri:catgirl.cloudbri

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

mkdir -p $out/nix-support
echo "file binary-dist \"$(echo $out/*.apk)\"" \
    > $out/nix-support/hydra-build-products

which i see is a bash script, so does that sort of thing need to be run by the runCommand? i assume $out is set by hydra/nix?

20:50:45
@tomberek:matrix.orgtomberek

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:

hydraJobs = {
my-other-job = runCommand ....;
...
}
20:56:11
@bri:catgirl.cloudbri

right now my hydraJobs is ```nix
hydraJobs = {
serverProxmox = self.nixosConfigurations."server@x86_64-linux".config.formats.proxmox;
serverProxmoxLxc = self.nixosConfigurations."server@x86_64-linux".config.formats.proxmox-lxc;
briRawEfi = self.nixosConfigurations."bri@x86_64-linux".config.formats.raw-efi;
};

(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?
20:59:59
@bri:catgirl.cloudbri *

right now my hydraJobs is

hydraJobs = {
serverProxmox = self.nixosConfigurations."server@x86\_64-linux".config.formats.proxmox;
serverProxmoxLxc = self.nixosConfigurations."server@x86\_64-linux".config.formats.proxmox-lxc;
briRawEfi = self.nixosConfigurations."bri@x86\_64-linux".config.formats.raw-efi;
};

(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
@bri:catgirl.cloudbri *

right now my hydraJobs is

hydraJobs = {
serverProxmox = self.nixosConfigurations."server@x86\_64-linux".config.formats.proxmox;
serverProxmoxLxc = self.nixosConfigurations."server@x86\_64-linux".config.formats.proxmox-lxc;
briRawEfi = self.nixosConfigurations."bri@x86\_64-linux".config.formats.raw-efi;
};

(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
@bri:catgirl.cloudbri 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
@bri:catgirl.cloudbri * 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
@ygt:matrix.org@ygt:matrix.org joined the room.00:13:34
@delroth:delroth.net@delroth:delroth.netcan 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
@5m5z3q888q5prxkg:chat.lightnovel-dungeon.de@5m5z3q888q5prxkg:chat.lightnovel-dungeon.de changed their profile picture.03:28:34
@k900:0upti.meK900Oh yeah probably should post it here too https://github.com/NixOS/hydra/pull/136415:50:25
@k900:0upti.meK900I'm pretty sure I got it right15:50:35
@k900:0upti.meK900But I don't have a Hydra to test on15:50:43
@k900:0upti.meK900But I did copy the urlencode incantation15:51:01
@k900:0upti.meK900* But I did copy the urlencode incantation from another place in Hydra where it presumably works15:51:09
@fedx:matrix.orgfedx left the room.16:46:46
26 Feb 2024
@martiert:matrix.orgmartiert joined the room.06:53:11
@martiert:matrix.orgmartiert 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
@tomberek:matrix.orgtomberek"nix path-info --json" can show you the signatures. How are you signing the packages right now in Hydra?11:32:49
@martiert:matrix.orgmartiert 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
@martiert:matrix.orgmartiertor am I completely misunderstanding this part?12:21:59
@martiert:matrix.orgmartierthmmm.. Guess I have missunderstood, as stuff is not signed12:23:22
@tomberek:matrix.orgtomberekThat 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
@martiert:matrix.orgmartiertack, thanks. I'll look at that13:04:03
@martiert:matrix.orgmartiert is it valid to say store_uri = file:///nix/store?secret-key=/my/secret/key? 13:07:10
@tomberek:matrix.orgtomberekYes, but if memory serves, you may want "local?secret-key..." so that it talks to the daemon.18:04:49
@martiert:matrix.orgmartiert store_uri = "local?secret-key=..." gives me error: don't know how to open Nix store 18:15:38
@martiert:matrix.orgmartiert should it be localhost, or maybe s3://localhost ? 18:15:56

Show newer messages


Back to Room ListRoom Version: 6