nixinate/tests/default.nix

{ pkgs
, makeTest
, inputs
,
}: {
  vmTestLocal = (import ./vmTest { inherit pkgs makeTest inputs; }).local;
  vmTestRemote = (import ./vmTest { inherit pkgs makeTest inputs; }).remote;
  vmTestLocalHermetic = (import ./vmTest { inherit pkgs makeTest inputs; }).localHermetic;
  vmTestRemoteHermetic = (import ./vmTest { inherit pkgs makeTest inputs; }).remoteHermetic;
}
Run nixpkgs-fmt 2023-12-11 20:37:06 +01:00			`{ pkgs`
			`, makeTest`
			`, inputs`
			`,`
			`}: {`
make vmTestLocal and vmTestRemote This creates and uses a function named mkNixinateTest which takes a buildOn argument. This expects to be either "local" or "remote". This means we can make a test for both use cases of Nixinate. One where we build on the remote machine, and one where we build locally and push to the remote machine. These tests are then added to the top level of the tests folder and are imported by the flake.nix 2022-04-21 02:08:02 +01:00			`vmTestLocal = (import ./vmTest { inherit pkgs makeTest inputs; }).local;`
			`vmTestRemote = (import ./vmTest { inherit pkgs makeTest inputs; }).remote;`
Fix hermetic remote builds and tests In the previous attempt to add this feature, I had forgotten to add the new tests to tests/default.nix, which meant I believed the feature worked when it did not. Additionally, real world testing shows that if the path does not exist on the remote already, that nix build --store will not work and will throw the following error: 'path '/nix/store/foo' is required, but there is no substituter that can build it' To fix this, I've decided to use nix copy --derivation and then nix-store --realise on the remote. A lot of refactoring is needed to make this codebase presentable anyway, so this hack is fine for now, though it is admittedly an unclean implementation. 2022-06-02 00:55:49 +01:00			`vmTestLocalHermetic = (import ./vmTest { inherit pkgs makeTest inputs; }).localHermetic;`
			`vmTestRemoteHermetic = (import ./vmTest { inherit pkgs makeTest inputs; }).remoteHermetic;`
Add vmTest for Nixinate This initializes ./test/default.nix which is referred to by the flake.nix under the `checks` attribute. This default.nix should point to all future tests, where they can be looked up and ran like: nix build .#checks.x86_64-linux.vmTest The test included is a simple NixOS VM Test. It uses Nixinate to deploy a machine with `services.nginx.enable = true` set, and tests whether nginx.service is started and reachable after deployment. 2022-03-31 20:36:59 +01:00			`}`