Graham Christensen

Hmm... it looks like this isn't always right, because Hydra's evaluator will fall back to `.checks` if `hydraJobs` isn't available: https://github.com/NixOS/hydra/blob/1124230d9f6d482481ddb5316d14e19828a0ab57/src/hydra-eval-jobs/hydra-eval-jobs.cc#L118-L122 I wonder if there is something we could do...

I'm not sure it is a good idea to bring back jobset inputs like this. I wonder if it would make more sense to have plugin configuration be a different...

Concretely, I can imagine someone being confused about why their jobset inputs aren't available to their jobset. Also, it causes perhaps internal confusion about if the inputs should be fetched,...

@Ma27 do you have a few hundred gigabytes of free space to try out the migration on the prod dataset? If so, I can get you a copy.

I'm going to post about this on the Hydra section of Discourse.

Looks like we should use `nix flake metadata` instead.

I don't know if it works, but it compiles.

Nice, if you wanted to implement a fix for that, you could start by writing a test here: https://github.com/NixOS/hydra/blob/master/t/scripts/hydra-create-user.t

@tomberek did you intend for this to be a draft PR?

from clever on IRC: > when hydra does a new eval, the old version reports the lowest build# it just added in the eval. so, if a given eval creates...