4 commits

Author	SHA1	Message	Date
vicky1999	a0f071f1d3	store info sh renamed	2023-10-18 00:12:10 +05:30
Ninlives	94e91566ed	Allow CLI to pass environment variables to FOD builder (#8830) ... Add a new experimental `impure-env` setting that is a key-value list of environment variables to inject into FOD derivations that specify the corresponding `impureEnvVars`. This allows clients to make use of this feature (without having to change the environment of the daemon itself) and might eventually deprecate the current behaviour (pick whatever is in the environment of the daemon) as it's more principled and might prevent information leakage.	2023-10-11 11:58:42 +00:00
John Ericson	47b3508665	Use positive source filtering for the standalone functional tests job ... Additionally this skipping of the building is reimplemented to be a bit more robust and use the same idioms as the functionality for skipping the tests. In particular, it will now work even if the source files exist, so we can do this during development too.	2023-10-09 08:29:27 -04:00
John Ericson	68c81c7375	Put functional tests in tests/functional ... I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```	2023-10-06 09:05:56 -04:00

Renamed from tests/local.mk (Browse further)