Look at some cross derivations too.
We already instantiate the moral equivalent of https://hydra.nixos.org/jobset/nixpkgs/trunk, it would be nice to do https://hydra.nixos.org/jobset/nixpkgs/cross-trunk too. The job is at pkgs/top-level/release-cross.nix.
In response to some IRC discussion, I was asked to elaborate a bit on this issue. @Ericson2314 please confirm or elaborate further with anything you think relevant/helpful here.
I think this is relatively straightforward in that an implementation of this would evaluate the mentioned release-cross.nix for nixpkgs evaluations, in addition to the currently used release.nix.
(note: are the commands shown in README accurate regarding what actually is executed? I asked because it appears https://github.com/NixOS/ofborg/blob/released/ofborg/src/outpaths.nix is what's used instead, or for something else?)
Anyway release-cross.nix is invoked very much like release.nix.
Making this work reasonably with the current workflow might take a bit of touching up, as it'd probably be useful to report cross issues separately or perhaps only run them optionally (??). Also if we're still approaching evaluation resource limits (memory usage?) this might need to be done in a separate invocation or something...
@dtzWill That all sounds good to me. Since I've made this issue, I've decided I'd like to add some/all of release-cross.nix to release.nix, and making it part of nixpkgs-unstable too. That's a bigger change, but also less work for the ofborg end of things.