!zghijEASpYQWYFzriI:nixos.org

Hydra

390 Members
109 Servers

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


SenderMessageTime
17 Aug 2022
@linus:schreibt.jetzt@linus:schreibt.jetzt(but yes if they want to build them locally)10:27:41
@leons:is.currently.online@leons:is.currently.onlineThanks for this advice! I'll see how I can make it work :D10:29:52
@enemycube:matrix.orgenemycube joined the room.17:03:16
@bradbqc1:matrix.orgBrad Bondurant joined the room.17:25:07
@bradbqc1:matrix.orgBrad Bondurant +1 for extra-sandbox-paths, also check out buildFHSUserEnv for running binaries that expect FHS paths to be present. Here's an example environment for Vivado https://git.m-labs.hk/M-Labs/nix-scripts/src/branch/master/artiq-fast/vivado.nix 17:31:01
@bradbqc1:matrix.orgBrad Bondurant Also, has anyone figured out a good way to do proper CI/CD with Hydra using flakes? I have several repositories, each with their own flake, and then a central flake that pulls them in and defines the hydraJobs. With legacy builds it was easy - just specify a repository as an input, and as long as the revision isn't pinned then any new commits will trigger a build. In addition to the restrictive lock flags Hydra uses (https://github.com/NixOS/hydra/issues/1160), it seems that flake support is just... bad. e.g. flake inputs aren't even recorded in Hydra's DB. I've been working on patches to Hydra to allow "unlocked" flakes, but that's a good chunk of work and I'm wondering if I can hack something else together more easily. 17:38:11
@bradbqc1:matrix.orgBrad Bondurant One idea I've had is to have a separate jobset that just does something like a nix flake update and copies the flake.nix and flake.lock to the output, and then use that flake as the input for the real jobset, but I'm not sure if that's doable 17:40:03
@bradbqc1:matrix.orgBrad BondurantAnd the absolute hackiest idea I've had is to put the flake in a local file on the server and make a cron job that updates it periodically17:42:07
@casey:hubns.netcransomi don't know if i'm up to date with all the methods, but i think the current general practice was something like your cron job - another task that runs nix flake update, commits, and pushes.17:44:50
@bradbqc1:matrix.orgBrad Bondurantthat's a bummer :/ talk about a messy git history17:47:57
@greaka:greaka.degreaka joined the room.20:18:07

Show newer messages


Back to Room ListRoom Version: 6