overview: use NIX_CONFIG from CI tests#1017
Conversation
|
|
this is much less noisy
that way we can access it easily from Nix code for use in documentation
fricklerhandwerk
force-pushed
the
simplify-caching
branch
from
8349330 to
e05237a
Compare
fricklerhandwerk
force-pushed
the
simplify-caching
branch
from
e05237a to
10f59b0
Compare
this is much less noisy
|
Some changes here are causing CI to attempt building the overview for aarch64, whereas the machine is x86_64. |
…s into simplify-caching
|
Depends on #1092 |
fricklerhandwerk
changed the title
|
@erictapen wdyt about the IFD? Not nice I know, but we won't suddenly have a pure Nix YAML parser. |
| readFile (pkgs.runCommandNoCC "yaml.json" { } "${lib.getExe pkgs.yj} < ${file} > $out") | ||
| ); | ||
| workflow = from-yaml ../.github/workflows/test-demo.yaml; | ||
| nix-config = with lib; trim (elemAt workflow.jobs.test.steps 3).env.NIX_CONFIG; |
There was a problem hiding this comment.
We may want to have some assertion here that the string starts with extra- or something, such that changing the order of entries won't have surprising effects on the overview.
Why don't we do it the other way around, and have the CI test use a generated |
|
Ah, like we evaluate the Nixpkgs revision? |
It would be as we discussed earlier today for the |
3 participants
this is much less noisy. @imincik any reason not to do it that way?