ilyakooo0/nixpkgs
1
0
Fork 0
mirror of https://github.com/ilyakooo0/nixpkgs.git synced 2024-12-27 05:43:50 +03:00
Code Issues Projects Releases Wiki Activity
8f789693d4
nixpkgs/nixos/release.nix

406 lines
16 KiB
Nix
Raw Normal View History

nixos/release*.nix: Clean nixpkgs sources by default Currently, when building NixOS from a git clone, Nix has to copy the entire repo at >1GB into the store by default. That is not necessary and causes a dumping large path message. If you need the old behaviour for some reason, you will have to specify it by passing the path to your repo explicitly as the nixpkgs argument like this: --arg nixpkgs '{outPath = ./.; revCount = 56789; shortRev = "gfedcba"; }'
2018-02-01 12:34:03 +03:00
{ nixpkgs ? { outPath = (import ../lib).cleanSource ./..; revCount = 56789; shortRev = "gfedcba"; }
Tweak the version string It's now "<yy>.<mm>pre<commit-count>.<short-hash>" (e.g. "13.10pre5678.gfedcba") for the unstable branch, and "<yy>.<mm>.<commit-count>.<short-hash>" (e.g. "13.10.5678.gfedcba") for stable branches.
2013-10-10 14:16:20 +04:00
, stableBranch ? false
Netboot: Add aarch64
2017-04-15 00:59:54 +03:00
, supportedSystems ? [ "x86_64-linux" "aarch64-linux" ]
* Generate a NixOS channel. svn path=/nixos/trunk/; revision=33684
2012-04-09 16:49:03 +04:00
}:
* Move the nixosSrc argument to top level. svn path=/nixos/trunk/; revision=33619
2012-04-05 17:00:30 +04:00
nixos/release.nix: Move forAllSystems to release-lib There's already a similar forTheseSystems in release-lib, so be more consistent.
2018-01-16 19:29:43 +03:00
with import ../pkgs/top-level/release-lib.nix { inherit supportedSystems; };
Rename scrubDrv -> hydraJob and make it more effective It now strictly evaluates all remaining attributes, preventing unevaluated thunks that cannot be garbage-collected. It's also applied to all jobs in Nixpkgs' release.nix. This reduces hydra-eval-jobs' memory consumption on the 14.12 release-combined jobset from 5.1 GB to 2.0 GB.
2015-03-20 21:23:55 +03:00
with import ../lib;
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
let
release.nix: refactor with fileContents
2016-07-31 16:05:38 +03:00
version = fileContents ../.version;
Tweak the version string It's now "<yy>.<mm>pre<commit-count>.<short-hash>" (e.g. "13.10pre5678.gfedcba") for the unstable branch, and "<yy>.<mm>.<commit-count>.<short-hash>" (e.g. "13.10.5678.gfedcba") for stable branches.
2013-10-10 14:16:20 +04:00
versionSuffix =
release.nix: Drop officialRelease flag
2014-05-01 16:52:07 +04:00
(if stableBranch then "." else "pre") + "${toString nixpkgs.revCount}.${nixpkgs.shortRev}";
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
nixos/release.nix: Add a callSubTests function This should de-clutter the various redundant lines of callTest's on subtests so that every main test file should have only one line with a callSubTests instead. Overrides work the same way as callTest, except that if the system attribute is explicitly specified we do not generate attributes for all available systems. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra
2016-02-29 22:02:26 +03:00
importTest = fn: args: system: import fn ({
inherit system;
} // args);
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
callTestOnTheseSystems = systems: fn: args: forTheseSystems systems (system: hydraJob (importTest fn args system));
callTest = callTestOnTheseSystems supportedSystems;
nixos/release.nix: Add a callSubTests function This should de-clutter the various redundant lines of callTest's on subtests so that every main test file should have only one line with a callSubTests instead. Overrides work the same way as callTest, except that if the system attribute is explicitly specified we do not generate attributes for all available systems. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra
2016-02-29 22:02:26 +03:00
nixos/release.nix: Introduce callSubTestsOnTheseSystems The existing callSubTests seems to already have special-cased code to allow enabling subtests on a single specific system by looking at the `system` attribute in the test arguments. Replace it with a new version similar to the callTestOnTheseSystems because: - It's consistent with the existing functions for creating system-specific tests (though admittedly, the callSubTests special case for `system` predates them) - This approach allows limiting to multiple system types, the previous one inherently allows only one system type. - This also fixes the problem that if you pass in e.g. supportedSystems = [ "aarch64-linux" ], you end up with a tests.chromium job that silently runs on x86_64-linux. - Finally, this causes renames of the jobs like: tests.chromium -> tests.chromium.x86_64-linux to be consistent with the rest of the tests.
2018-01-23 00:19:06 +03:00
callSubTests = callSubTestsOnTheseSystems supportedSystems;
callSubTestsOnTheseSystems = systems: fn: args: let
nixos/release.nix: Add a callSubTests function This should de-clutter the various redundant lines of callTest's on subtests so that every main test file should have only one line with a callSubTests instead. Overrides work the same way as callTest, except that if the system attribute is explicitly specified we do not generate attributes for all available systems. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra
2016-02-29 22:02:26 +03:00
discover = attrs: let
subTests = filterAttrs (const (hasAttr "test")) attrs;
in mapAttrs (const (t: hydraJob t.test)) subTests;
discoverForSystem = system: mapAttrs (_: test: {
${system} = test;
}) (discover (importTest fn args system));
nixos/release.nix: Introduce callSubTestsOnTheseSystems The existing callSubTests seems to already have special-cased code to allow enabling subtests on a single specific system by looking at the `system` attribute in the test arguments. Replace it with a new version similar to the callTestOnTheseSystems because: - It's consistent with the existing functions for creating system-specific tests (though admittedly, the callSubTests special case for `system` predates them) - This approach allows limiting to multiple system types, the previous one inherently allows only one system type. - This also fixes the problem that if you pass in e.g. supportedSystems = [ "aarch64-linux" ], you end up with a tests.chromium job that silently runs on x86_64-linux. - Finally, this causes renames of the jobs like: tests.chromium -> tests.chromium.x86_64-linux to be consistent with the rest of the tests.
2018-01-23 00:19:06 +03:00
in foldAttrs mergeAttrs {} (map discoverForSystem (intersectLists systems supportedSystems));
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
Update the release expressions and the channel generators
2013-10-01 17:48:39 +04:00
pkgs = import nixpkgs { system = "x86_64-linux"; };
* Consistently include the Nixpkgs revision in the NixOS version string. svn path=/nixos/trunk/; revision=33729
2012-04-11 00:28:06 +04:00
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
Set the version of the VirtualBox image properly
2013-07-02 15:33:27 +04:00
versionModule =
nixos: rename config.system.nixos* -> config.system.nixos.*
2017-04-01 03:00:00 +03:00
{ system.nixos.versionSuffix = versionSuffix;
system.nixos.revision = nixpkgs.rev or nixpkgs.shortRev;
Ensure that the manual job gets build with the right revision info
2013-10-24 21:58:34 +04:00
};
Set the version of the VirtualBox image properly
2013-07-02 15:33:27 +04:00
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
makeIso =
Combine ISO generation steps This folds adding hydra-build-products into the actual ISO generation, preventing an unnecessary download of the ISO.
2016-03-15 15:48:45 +03:00
{ module, type, maintainers ? ["eelco"], system }:
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
Update the release expressions and the channel generators
2013-10-01 17:48:39 +04:00
with import nixpkgs { inherit system; };
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
Combine ISO generation steps This folds adding hydra-build-products into the actual ISO generation, preventing an unnecessary download of the ISO.
2016-03-15 15:48:45 +03:00
hydraJob ((import lib/eval-config.nix {
inherit system;
modules = [ module versionModule { isoImage.isoBaseName = "nixos-${type}"; } ];
}).config.system.build.isoImage);
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
makeSystemTarball =
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
{ module, maintainers ? ["viric"], system }:
Update the release expressions and the channel generators
2013-10-01 17:48:39 +04:00
with import nixpkgs { inherit system; };
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
let
config = (import lib/eval-config.nix {
* Fix the NixOS jobset. svn path=/nixos/trunk/; revision=32783
2012-03-05 00:57:34 +04:00
inherit system;
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
modules = [ module versionModule ];
}).config;
tarball = config.system.build.tarball;
Set the version of the VirtualBox image properly
2013-07-02 15:33:27 +04:00
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
in
tarball //
{ meta = {
description = "NixOS system tarball for ${system} - ${stdenv.platform.name}";
Rename scrubDrv -> hydraJob and make it more effective It now strictly evaluates all remaining attributes, preventing unevaluated thunks that cannot be garbage-collected. It's also applied to all jobs in Nixpkgs' release.nix. This reduces hydra-eval-jobs' memory consumption on the 14.12 release-combined jobset from 5.1 GB to 2.0 GB.
2015-03-20 21:23:55 +03:00
maintainers = map (x: lib.maintainers.${x}) maintainers;
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
};
inherit config;
};
Fix the manual jobs
2014-09-18 18:21:00 +04:00
makeClosure = module: buildFromConfig module (config: config.system.build.toplevel);
Rename scrubDrv -> hydraJob and make it more effective It now strictly evaluates all remaining attributes, preventing unevaluated thunks that cannot be garbage-collected. It's also applied to all jobs in Nixpkgs' release.nix. This reduces hydra-eval-jobs' memory consumption on the 14.12 release-combined jobset from 5.1 GB to 2.0 GB.
2015-03-20 21:23:55 +03:00
buildFromConfig = module: sel: forAllSystems (system: hydraJob (sel (import ./lib/eval-config.nix {
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
inherit system;
Rename scrubDrv -> hydraJob and make it more effective It now strictly evaluates all remaining attributes, preventing unevaluated thunks that cannot be garbage-collected. It's also applied to all jobs in Nixpkgs' release.nix. This reduces hydra-eval-jobs' memory consumption on the 14.12 release-combined jobset from 5.1 GB to 2.0 GB.
2015-03-20 21:23:55 +03:00
modules = [ module versionModule ] ++ singleton
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
({ config, lib, ... }:
Rename scrubDrv -> hydraJob and make it more effective It now strictly evaluates all remaining attributes, preventing unevaluated thunks that cannot be garbage-collected. It's also applied to all jobs in Nixpkgs' release.nix. This reduces hydra-eval-jobs' memory consumption on the 14.12 release-combined jobset from 5.1 GB to 2.0 GB.
2015-03-20 21:23:55 +03:00
{ fileSystems."/".device = mkDefault "/dev/sda1";
boot.loader.grub.device = mkDefault "/dev/sda";
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
});
Fix the manual jobs
2014-09-18 18:21:00 +04:00
}).config));
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
Netboot: Add aarch64
2017-04-15 00:59:54 +03:00
makeNetboot = config:
let
nixos/release.nix: Clean some syntax
2018-01-11 19:46:49 +03:00
configEvaled = import lib/eval-config.nix config;
build = configEvaled.config.system.build;
kernelTarget = configEvaled.pkgs.stdenv.platform.kernelTarget;
Netboot: Add aarch64
2017-04-15 00:59:54 +03:00
in
pkgs.symlinkJoin {
nixos/release.nix: Clean some syntax
2018-01-11 19:46:49 +03:00
name = "netboot";
paths = [
Netboot: Add aarch64
2017-04-15 00:59:54 +03:00
build.netbootRamdisk
build.kernel
build.netbootIpxeScript
];
postBuild = ''
mkdir -p $out/nix-support
echo "file ${kernelTarget} $out/${kernelTarget}" >> $out/nix-support/hydra-build-products
echo "file initrd $out/initrd" >> $out/nix-support/hydra-build-products
echo "file ipxe $out/netboot.ipxe" >> $out/nix-support/hydra-build-products
'';
nixos/release.nix: Add preferLocalBuild to makeNetboot result
2018-01-11 19:47:23 +03:00
preferLocalBuild = true;
Netboot: Add aarch64
2017-04-15 00:59:54 +03:00
};
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
Simplify manual generation
2013-10-24 21:31:51 +04:00
in rec {
* Hydra release expression for building NixOS. svn path=/nixos/trunk/; revision=13651
2008-12-17 16:25:23 +03:00
Factor the NixOS channel building code out into its own file, so I can use it elsewhere
2015-06-14 04:55:29 +03:00
channel = import lib/make-channel.nix { inherit pkgs nixpkgs version versionSuffix; };
* Build the Subversion test in Hydra (as a regression test for NixOS). * Pass the location to the services tree around instead of requiring it to be in ../services. svn path=/nixos/trunk/; revision=16901
2009-08-31 18:56:19 +04:00
Revert "Merge #12357: nixos docs: show references to packages" The PR wasn't good enough yet. This reverts commit b2a37ceeea8c38ec71447f8dae1e6890a8cf982d, reversing changes made to 7fa9a1abce623aaf18b22f5dca3fc8a44a494e8d.
2016-02-03 14:16:33 +03:00
manual = buildFromConfig ({ pkgs, ... }: { }) (config: config.system.build.manual.manual);
add epub for NixOS manual (second try) (#17205)
2016-07-28 05:27:39 +03:00
manualEpub = (buildFromConfig ({ pkgs, ... }: { }) (config: config.system.build.manual.manualEpub));
Revert "Merge #12357: nixos docs: show references to packages" The PR wasn't good enough yet. This reverts commit b2a37ceeea8c38ec71447f8dae1e6890a8cf982d, reversing changes made to 7fa9a1abce623aaf18b22f5dca3fc8a44a494e8d.
2016-02-03 14:16:33 +03:00
manpages = buildFromConfig ({ pkgs, ... }: { }) (config: config.system.build.manual.manpages);
options = (buildFromConfig ({ pkgs, ... }: { }) (config: config.system.build.manual.optionsJSON)).x86_64-linux;
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
Add a Hydra job to track the size of the initrd
2014-10-09 20:40:37 +04:00
# Build the initial ramdisk so Hydra can keep track of its size over time.
initialRamdisk = buildFromConfig ({ pkgs, ... }: { }) (config: config.system.build.initialRamdisk);
nixos/release.nix: Use forTheseSystems from release-lib Currently, even if you pass `supportedSystems = [ "aarch64-linux" ]` you end up with e.g. `nixos.iso_graphical.x86_64-linux` job. Using forTheseSystems from release-lib avoids that. This shouldn't affect the usual x86 trunk-combined jobset.
2018-01-16 19:42:47 +03:00
netboot = forTheseSystems [ "x86_64-linux" "aarch64-linux" ] (system: makeNetboot {
inherit system;
modules = [
./modules/installer/netboot/netboot-minimal.nix
versionModule
];
});
installer: simple PXE bootable NixOS installer The Nix store squashfs is stored inside the initrd instead of separately (cherry picked from commit 976fd407796877b538c470d3a5253ad3e1f7bc68) Signed-off-by: Domen Kožar <domen@dev.si>
2016-04-08 16:53:27 +03:00
Generate manual for i686-linux as well as x86_64-linux
2013-10-31 11:48:57 +04:00
iso_minimal = forAllSystems (system: makeIso {
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
module = ./modules/installer/cd-dvd/installation-cd-minimal.nix;
type = "minimal";
inherit system;
iso_minimal_new_kernel
2013-04-06 20:24:12 +04:00
});
nixos/release.nix: Use forTheseSystems from release-lib Currently, even if you pass `supportedSystems = [ "aarch64-linux" ]` you end up with e.g. `nixos.iso_graphical.x86_64-linux` job. Using forTheseSystems from release-lib avoids that. This shouldn't affect the usual x86 trunk-combined jobset.
2018-01-16 19:42:47 +03:00
iso_graphical = forTheseSystems [ "x86_64-linux" ] (system: makeIso {
installer: add graphical GNOME iso
2015-10-08 15:53:37 +03:00
module = ./modules/installer/cd-dvd/installation-cd-graphical-kde.nix;
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
type = "graphical";
inherit system;
});
# A variant with a more recent (but possibly less stable) kernel
# that might support more hardware.
nixos/release.nix: Use forTheseSystems from release-lib Currently, even if you pass `supportedSystems = [ "aarch64-linux" ]` you end up with e.g. `nixos.iso_graphical.x86_64-linux` job. Using forTheseSystems from release-lib avoids that. This shouldn't affect the usual x86 trunk-combined jobset.
2018-01-16 19:42:47 +03:00
iso_minimal_new_kernel = forTheseSystems [ "x86_64-linux" ] (system: makeIso {
nixos-iso: Re-enable new kernel iso images (close #2839)
2014-06-06 01:00:25 +04:00
module = ./modules/installer/cd-dvd/installation-cd-minimal-new-kernel.nix;
type = "minimal-new-kernel";
inherit system;
});
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
Generate a VirtualBox appliance (in OVF format) instead of a disk image
2013-10-08 17:40:48 +04:00
# A bootable VirtualBox virtual appliance as an OVA file (i.e. packaged OVF).
nixos/release.nix: Use forTheseSystems from release-lib Currently, even if you pass `supportedSystems = [ "aarch64-linux" ]` you end up with e.g. `nixos.iso_graphical.x86_64-linux` job. Using forTheseSystems from release-lib avoids that. This shouldn't affect the usual x86 trunk-combined jobset.
2018-01-16 19:42:47 +03:00
ova = forTheseSystems [ "x86_64-linux" ] (system:
Build 32-bit VirtualBox image Issue #200.
2013-08-26 16:06:00 +04:00
Update the release expressions and the channel generators
2013-10-01 17:48:39 +04:00
with import nixpkgs { inherit system; };
release.nix: Generate a VirtualBox image
2013-07-02 02:23:48 +04:00
Combine OVA generation steps Previously this was done in three derivations (one to build the raw disk image, one to convert to OVA, one to add a hydra-build-products file). Now it's done in one step to reduce the amount of copying to/from S3. In particular, not uploading the raw disk image prevents us from hitting hydra-queue-runner's size limit of 2 GiB.
2016-03-15 15:34:41 +03:00
hydraJob ((import lib/eval-config.nix {
inherit system;
modules =
[ versionModule
./modules/installer/virtualbox-demo.nix
];
}).config.system.build.virtualBoxOVA)
Build 32-bit VirtualBox image Issue #200.
2013-08-26 16:06:00 +04:00
);
release.nix: Generate a VirtualBox image
2013-07-02 02:23:48 +04:00
Add all default NixOS packages to the channel The job ‘dummy’ depends on the default contents of ‘environment.systemPackages’, thus ensuring that those packages all end up in the channel.
2014-09-25 02:20:53 +04:00
# Ensure that all packages used by the minimal NixOS config end up in the channel.
dummy = forAllSystems (system: pkgs.runCommand "dummy"
Add an entire NixOS build to the channel This causes some cruft to be uploaded (such as unit files) but it ensures that every package used by the base system ends up in the channel, not just environment.systemPackages. (cherry picked from commit 4dfca8e14a5d1c2e62bb5ad267163a7a32ef872f)
2014-09-25 19:51:09 +04:00
{ toplevel = (import lib/eval-config.nix {
Add all default NixOS packages to the channel The job ‘dummy’ depends on the default contents of ‘environment.systemPackages’, thus ensuring that those packages all end up in the channel.
2014-09-25 02:20:53 +04:00
inherit system;
Rename scrubDrv -> hydraJob and make it more effective It now strictly evaluates all remaining attributes, preventing unevaluated thunks that cannot be garbage-collected. It's also applied to all jobs in Nixpkgs' release.nix. This reduces hydra-eval-jobs' memory consumption on the 14.12 release-combined jobset from 5.1 GB to 2.0 GB.
2015-03-20 21:23:55 +03:00
modules = singleton ({ config, pkgs, ... }:
{ fileSystems."/".device = mkDefault "/dev/sda1";
boot.loader.grub.device = mkDefault "/dev/sda";
Add an entire NixOS build to the channel This causes some cruft to be uploaded (such as unit files) but it ensures that every package used by the base system ends up in the channel, not just environment.systemPackages. (cherry picked from commit 4dfca8e14a5d1c2e62bb5ad267163a7a32ef872f)
2014-09-25 19:51:09 +04:00
});
}).config.system.build.toplevel;
Add some preferLocalBuild
2015-12-29 19:21:49 +03:00
preferLocalBuild = true;
Add all default NixOS packages to the channel The job ‘dummy’ depends on the default contents of ‘environment.systemPackages’, thus ensuring that those packages all end up in the channel.
2014-09-25 02:20:53 +04:00
}
Add an entire NixOS build to the channel This causes some cruft to be uploaded (such as unit files) but it ensures that every package used by the base system ends up in the channel, not just environment.systemPackages. (cherry picked from commit 4dfca8e14a5d1c2e62bb5ad267163a7a32ef872f)
2014-09-25 19:51:09 +04:00
"mkdir $out; ln -s $toplevel $out/dummy");
Add all default NixOS packages to the channel The job ‘dummy’ depends on the default contents of ‘environment.systemPackages’, thus ensuring that those packages all end up in the channel.
2014-09-25 02:20:53 +04:00
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
# Provide a tarball that can be unpacked into an SD card, and easily
# boot that system from uboot (like for the sheevaplug).
# The pc variant helps preparing the expression for the system tarball
# in a machine faster than the sheevpalug
Disable system_tarball_pc and fix eval It refers to a kernel version that no longer exists. (cherry picked from commit e4b9624ca89617005cb082e2a8301695759e1b19)
2015-06-15 15:18:27 +03:00
/*
Generate manual for i686-linux as well as x86_64-linux
2013-10-31 11:48:57 +04:00
system_tarball_pc = forAllSystems (system: makeSystemTarball {
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
module = ./modules/installer/cd-dvd/system-tarball-pc.nix;
inherit system;
});
Disable system_tarball_pc and fix eval It refers to a kernel version that no longer exists. (cherry picked from commit e4b9624ca89617005cb082e2a8301695759e1b19)
2015-06-15 15:18:27 +03:00
*/
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
nixos: container tarball release - Create container nixos profile - Create lxc-container nixos config using container nixos profile - Docker nixos image, use nixos profile for its base config
2014-12-12 00:58:17 +03:00
# Provide container tarball for lxc, libvirt-lxc, docker-lxc, ...
nixos: container profile, fix a few things
2014-12-12 22:28:01 +03:00
containerTarball = forAllSystems (system: makeSystemTarball {
nixos: container tarball release - Create container nixos profile - Create lxc-container nixos config using container nixos profile - Docker nixos image, use nixos profile for its base config
2014-12-12 00:58:17 +03:00
module = ./modules/virtualisation/lxc-container.nix;
inherit system;
});
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
/*
system_tarball_fuloong2f =
assert builtins.currentSystem == "mips64-linux";
makeSystemTarball {
module = ./modules/installer/cd-dvd/system-tarball-fuloong2f.nix;
system = "mips64-linux";
* By popular demand, provide an ISO with a more recent kernel. svn path=/nixos/trunk/; revision=30344
2011-11-08 23:51:39 +04:00
};
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
system_tarball_sheevaplug =
assert builtins.currentSystem == "armv5tel-linux";
makeSystemTarball {
module = ./modules/installer/cd-dvd/system-tarball-sheevaplug.nix;
system = "armv5tel-linux";
Build the efi-bootable cd on hydra svn path=/nixos/trunk/; revision=33152
2012-03-16 16:24:29 +04:00
};
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
*/
Revert "split release.nix into helpers and the jobs themselves". Change r32480 was made due to a misunderstanding. svn path=/nixos/trunk/; revision=32512
2012-02-23 16:00:05 +04:00
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
# Run the tests for each platform. You can run a test by doing
# e.g. ‘nix-build -A tests.login.x86_64-linux’, or equivalently,
# ‘nix-build tests/login.nix -A result’.
nixos/tests: add basic test for services.atd
2017-10-14 23:38:10 +03:00
tests.atd = callTest tests/atd.nix {};
nixos/tests: Add a basic test for ACME The test here is pretty basic and only tests nginx, but it should get us started to write tests for different webservers and different ACME implementations. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2017-07-27 14:24:17 +03:00
tests.acme = callTest tests/acme.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.avahi = callTest tests/avahi.nix {};
beegfs: init at 6.17 package, kernel module, nixos module, and nixos test
2017-12-29 04:51:42 +03:00
tests.beegfs = callTest tests/beegfs.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.bittorrent = callTest tests/bittorrent.nix {};
nixos: Add VM test for blivet. I'm really not sure whether these tests are actually run upstream, because there are quite a few oddities which either are my fault by just missing something important or upstream really doesn't bother to run those tests. One example of this are testDiskChunk1 and testDiskChunk2, which create two non-existing partitions and tries to allocate them. Now, in allocatePartitions(), the partedPartition attributes are reset to None and shortly afterwards a for loop is expecting it to be NOT None. So, for now I'm disabling these tests and will see if we stumble on them during work on nixpart 1.0, so we're really sure whether it's my fault or a real bug in blivet. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-10-22 07:50:33 +04:00
tests.blivet = callTest tests/blivet.nix {};
nixos/release: Use callSubTests for subtests Should clean up a lot of these redundant lines for various sub-tests. Note that the tests.boot* are now called tests.boot.boot*, but otherwise all the test attribute names should stay the same. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra Cc: @wkennington Cc: @bobvanderlinden
2016-02-29 22:11:04 +03:00
tests.boot = callSubTests tests/boot.nix {};
nixos/tests: Add a test for boot stage 1 We already have a small regression test for #15226 within the swraid installer test. Unfortunately, we only check there whether the md kthread got signalled but not whether other rampaging processes are still alive that *should* have been killed. So in order to do this we provide multiple canary processes which are checked after the system has booted up: * canary1: It's a simple forking daemon which just sleeps until it's going to be killed. Of course we expect this process to not be alive anymore after boot up. * canary2: Similar to canary1, but tries to mimick a kthread to make sure that it's going to be properly killed at the end of stage 1. * canary3: Like canary2, but this time using a @ in front of its command name to actually prevent it from being killed. * kcanary: This one is a real kthread and it runs until killed, which shouldn't be the case. Tested with and without 67223ee and everything works as expected, at least on my machine. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2016-05-06 17:06:22 +03:00
tests.boot-stage1 = callTest tests/boot-stage1.nix {};
nixos/borgbackup: add test We had problems to get borg's own test suite running. This test is intended to perform a quick smoke test to see whether we have missed not any important dependency necessary to create backups with borg. tested with: $ nix-build nixos/release.nix -A tests.borgbackup.x86_64-linux
2018-01-02 11:08:38 +03:00
tests.borgbackup = callTest tests/borgbackup.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
tests.cadvisor = callTestOnTheseSystems ["x86_64-linux"] tests/cadvisor.nix {};
nixos/release.nix: Introduce callSubTestsOnTheseSystems The existing callSubTests seems to already have special-cased code to allow enabling subtests on a single specific system by looking at the `system` attribute in the test arguments. Replace it with a new version similar to the callTestOnTheseSystems because: - It's consistent with the existing functions for creating system-specific tests (though admittedly, the callSubTests special case for `system` predates them) - This approach allows limiting to multiple system types, the previous one inherently allows only one system type. - This also fixes the problem that if you pass in e.g. supportedSystems = [ "aarch64-linux" ], you end up with a tests.chromium job that silently runs on x86_64-linux. - Finally, this causes renames of the jobs like: tests.chromium -> tests.chromium.x86_64-linux to be consistent with the rest of the tests.
2018-01-23 00:19:06 +03:00
tests.chromium = (callSubTestsOnTheseSystems ["x86_64-linux"] tests/chromium.nix {}).stable;
Revert "cjdns: Disable tests" This reverts commit 0ba3d429a758cec15545fc11c9d3fd1424c5c5f8.
2016-11-12 14:47:43 +03:00
tests.cjdns = callTest tests/cjdns.nix {};
nixos/cloudinit: add cloudinit test An iso containing metadatas is created and attached as a cdrom to the qemu VM used for this test. The cloudinit service is enabled. The test case ensures the root authorized_keys file is populated and the cloudinit write_file module is working well.
2017-02-25 17:32:06 +03:00
tests.cloud-init = callTest tests/cloud-init.nix {};
containers tests: Distinguish declarative and imperative containers
2016-03-18 17:29:45 +03:00
tests.containers-ipv4 = callTest tests/containers-ipv4.nix {};
containers: Add more tests for ipv6 and hostbridge A testcase each for - declarative ipv6-only container Seems odd to define the container IPs with their prefix length attached. There should be a better way… - declarative bridged container Also fix the ping test by waiting for the container to start When the ping was executed, the container might not have finished starting. Or the host-side of the container wasn't finished with config. Waiting for 2 seconds in between fixes this.
2016-01-31 23:45:05 +03:00
tests.containers-ipv6 = callTest tests/containers-ipv6.nix {};
tests.containers-bridge = callTest tests/containers-bridge.nix {};
containers tests: Distinguish declarative and imperative containers
2016-03-18 17:29:45 +03:00
tests.containers-imperative = callTest tests/containers-imperative.nix {};
declarative containers: additional veths With these changes, a container can have more then one veth-pair. This allows for example to have LAN and DMZ as bridges on the host and add dedicated containers for proxies, ipv4-firewall and ipv6-firewall. Or to have a bridge for normal WAN, one bridge for administration and one bridge for customer-internal communication. So that web-server containers can be reached from outside per http, from the management via ssh and can talk to their database via the customer network. The scripts to set up the containers are now rendered several times instead of just one template. The scripts now contain per-container code to configure the extra veth interfaces. The default template without support for extra-veths is still rendered for the imperative containers. Also a test is there to see if extra veths can be placed into host-bridges or can be reached via routing.
2016-05-07 01:04:28 +03:00
tests.containers-extra_veth = callTest tests/containers-extra_veth.nix {};
containers: Do not wait for udev for network devices Test that adding physical devices to containers works, find that network setup then doesn't work because there is no udev in the container to tell systemd that the device is present. Fixed by not depending on the device in the container. Activate the new container test for release Bonds, bridges and other network devices need the underlying not as dependency when used inside the container. Because the device is already there. But the address configuration needs the aggregated device itself.
2016-09-30 11:45:48 +03:00
tests.containers-physical_interfaces = callTest tests/containers-physical_interfaces.nix {};
network-interfaces: reload bridges on conf changes And adopt the tests to add an interface and remove it again. It should work when deactivating rstp, it will not work when activating rstp for the first bridge as then the userspace daemon is not yet available. But once one bridge is active with stp, it should work with the reload for any further bridge. Fixes #21745. Also see #22547.
2017-02-11 18:46:55 +03:00
tests.containers-restart_networking = callTest tests/containers-restart_networking.nix {};
nixos/release: add containers-tmpfs test cc #20557
2016-11-22 17:04:52 +03:00
tests.containers-tmpfs = callTest tests/containers-tmpfs.nix {};
containers: add tests for hosts and macvlans
2016-12-12 16:25:28 +03:00
tests.containers-hosts = callTest tests/containers-hosts.nix {};
tests.containers-macvlans = callTest tests/containers-macvlans.nix {};
nixos/tests: add couchdb test
2017-11-19 19:36:47 +03:00
tests.couchdb = callTest tests/couchdb.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
tests.docker = callTestOnTheseSystems ["x86_64-linux"] tests/docker.nix {};
nixos/tests: add simple dockerTools test
2018-02-14 08:20:16 +03:00
tests.docker-tools = callTestOnTheseSystems ["x86_64-linux"] tests/docker-tools.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
tests.docker-edge = callTestOnTheseSystems ["x86_64-linux"] tests/docker-edge.nix {};
nixos/dovecot: Fix createMailUser implementation This option got introduced in 7904499542814b8a4d04fce8dc7ca8c383c083e7 and it didn't check whether mailUser and mailGroup are null, which they are by default. Now we're only creating the user if createMailUser is set in conjunction with mailUser and the group if mailGroup is set as well. I've added a NixOS VM test so that we can verify whether dovecot works without any additional options set, so it serves as a regression test for issue #29466 and other issues that might come up with future changes to the Dovecot service. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Fixes: #29466 Cc: @qknight, @abbradar, @ixmatus, @siddharthist
2017-09-17 04:11:01 +03:00
tests.dovecot = callTest tests/dovecot.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
tests.dnscrypt-proxy = callTestOnTheseSystems ["x86_64-linux"] tests/dnscrypt-proxy.nix {};
ecryptfs: add test to release (#16910) Would have caught regression #16766
2016-07-13 15:57:13 +03:00
tests.ecryptfs = callTest tests/ecryptfs.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
tests.etcd = callTestOnTheseSystems ["x86_64-linux"] tests/etcd.nix {};
nixos/release.nix: Use callSubTestsOnTheseSystems for ec2 tests
2018-01-23 12:11:18 +03:00
tests.ec2-nixops = (callSubTestsOnTheseSystems ["x86_64-linux"] tests/ec2.nix {}).boot-ec2-nixops;
tests.ec2-config = (callSubTestsOnTheseSystems ["x86_64-linux"] tests/ec2.nix {}).boot-ec2-config;
nixos/release.nix: Introduce callSubTestsOnTheseSystems The existing callSubTests seems to already have special-cased code to allow enabling subtests on a single specific system by looking at the `system` attribute in the test arguments. Replace it with a new version similar to the callTestOnTheseSystems because: - It's consistent with the existing functions for creating system-specific tests (though admittedly, the callSubTests special case for `system` predates them) - This approach allows limiting to multiple system types, the previous one inherently allows only one system type. - This also fixes the problem that if you pass in e.g. supportedSystems = [ "aarch64-linux" ], you end up with a tests.chromium job that silently runs on x86_64-linux. - Finally, this causes renames of the jobs like: tests.chromium -> tests.chromium.x86_64-linux to be consistent with the rest of the tests.
2018-01-23 00:19:06 +03:00
tests.elk = callSubTestsOnTheseSystems ["x86_64-linux"] tests/elk.nix {};
tests: Add environment
2017-09-06 02:05:37 +03:00
tests.env = callTest tests/env.nix {};
ferm: add integration test
2016-08-29 16:18:25 +03:00
tests.ferm = callTest tests/ferm.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.firefox = callTest tests/firefox.nix {};
tests.firewall = callTest tests/firewall.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
tests.fleet = callTestOnTheseSystems ["x86_64-linux"] tests/fleet.nix {};
nixos tests: disable fwupd for now See https://github.com/NixOS/nixpkgs/pull/32751/files#r168736256
2018-02-16 14:42:57 +03:00
#tests.fwupd = callTest tests/fwupd.nix {}; # build during evaluation
nixos: disable gitlab test for now
2015-01-26 00:29:37 +03:00
#tests.gitlab = callTest tests/gitlab.nix {};
nixos/tests: add gitolite test
2017-10-14 11:42:37 +03:00
tests.gitolite = callTest tests/gitolite.nix {};
nixos/gjs: add test
2018-02-15 00:19:56 +03:00
tests.gjs = callTest tests/gjs.nix {};
Add gocd agent and server service packages (#16273) GoCD is an open source continuous delivery server specializing in advanced workflow modeling and visualization. Update maintainers list to include swarren83. Update module list to include gocd agent and server module. Update packages list to include gocd agent and server package. Update version, revision and checksum for GoCD release 16.5.0.
2016-07-23 01:29:18 +03:00
tests.gocd-agent = callTest tests/gocd-agent.nix {};
tests.gocd-server = callTest tests/gocd-server.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.gnome3 = callTest tests/gnome3.nix {};
nixos tests: add gdm test
2015-09-15 15:25:19 +03:00
tests.gnome3-gdm = callTest tests/gnome3-gdm.nix {};
nixos/tests: Fix typo (grafama -> grafana)
2017-10-21 23:44:15 +03:00
tests.grafana = callTest tests/grafana.nix {};
graphite: 0.9.15 -> 1.0.2 Fixes: #29961 Also added the option: services.graphite.web.extraConfig for configuring graphite_web.
2017-09-30 22:12:24 +03:00
tests.graphite = callTest tests/graphite.nix {};
nixos/tests: add tests for exercising various hardening features This test exercises the linux_hardened kernel along with the various hardening features (enabled via the hardened profile). Move hidepid test from misc, so that misc can go back to testing a vanilla configuration.
2017-04-30 09:38:47 +03:00
tests.hardened = callTest tests/hardened.nix { };
nixos/tests: add hibernation test
2015-03-05 17:21:27 +03:00
tests.hibernate = callTest tests/hibernate.nix {};
home-assistant: add NixOS test
2018-01-26 03:41:36 +03:00
tests.home-assistant = callTest tests/home-assistant.nix { };
hound: init module
2016-10-13 01:58:56 +03:00
tests.hound = callTest tests/hound.nix {};
nixos: Add VM test for i3 window manager. Currently just makes sure that by default it's possible to open a terminal. And exactly this should be the main point that might confuse users of i3 in NixOS, because i3 doesn't print a warning/error if it is unable to start the terminal emulator. Thanks to @waaaaargh for reporting this issue. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-03-05 07:16:26 +03:00
tests.i3wm = callTest tests/i3wm.nix {};
tests/initrd-network-ssh: Don't build during evaluation Issue #29774
2017-11-27 11:14:17 +03:00
tests.initrd-network-ssh = callTest tests/initrd-network-ssh {};
nixos/release: Use callSubTests for subtests Should clean up a lot of these redundant lines for various sub-tests. Note that the tests.boot* are now called tests.boot.boot*, but otherwise all the test attribute names should stay the same. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra Cc: @wkennington Cc: @bobvanderlinden
2016-02-29 22:11:04 +03:00
tests.installer = callSubTests tests/installer.nix {};
nixos: add influxdb module
2014-05-28 00:54:43 +04:00
tests.influxdb = callTest tests/influxdb.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.ipv6 = callTest tests/ipv6.nix {};
tests.jenkins = callTest tests/jenkins.nix {};
nixos/tests: fix Plasma 5 test
2017-03-01 04:09:56 +03:00
tests.plasma5 = callTest tests/plasma5.nix {};
nixos/plotinus: add module to enable plotinus
2018-02-14 23:34:50 +03:00
tests.plotinus = callTest tests/plotinus.nix {};
nixos/tests: Add a test for keyboard layouts I had the basic version of this laying around for some while but didn't continue on it. Originally it was for testing support for the Neo layout introduced back then (8cd6d53). We only test the first three Neo layers, because the last three layers are largely comprised of special characters and in addition to that the support for the VT keymap seems to be limited compared to the Xorg keymap. Yesterday @NicolasPetton on IRC had troubles with the Colemak layout (IRC logs: http://nixos.org/irc/logs/log.20160330, starting at 16:08) and I found that test again, so I went for improving and adding to <nixpkgs>. While the original problem seemed to be related to GDM, we can still add another subtest that checks whether GDM correctly applies the keyboard layout. However I don't have a clue how to properly configure the keyboard layout on GDM, at least not within the NixOS configuration. The main goal of this test is not to test a complete set of all key mappings but to check whether the keymap is loaded and working at all. It also serves as an example for NixOS keyboard configurations. The list of keyboard layouts is by no means complete, so everybody is free to add their own to the test or improve the existing ones. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2016-03-31 10:26:58 +03:00
tests.keymap = callSubTests tests/keymap.nix {};
boot.initrd.network: Support DHCP This allows us to use it for EC2 instances.
2016-02-02 21:03:13 +03:00
tests.initrdNetwork = callTest tests/initrd-network.nix {};
kafka: Add tests
2017-11-02 22:10:33 +03:00
tests.kafka_0_9 = callTest tests/kafka_0_9.nix {};
tests.kafka_0_10 = callTest tests/kafka_0_10.nix {};
tests.kafka_0_11 = callTest tests/kafka_0_11.nix {};
tests.kafka_1_0 = callTest tests/kafka_1_0.nix {};
tests: Fix copperhead call
2017-09-08 02:43:51 +03:00
tests.kernel-copperhead = callTest tests/kernel-copperhead.nix {};
nixos/release*: fixup evaluation of the tested job
2017-09-07 22:11:06 +03:00
tests.kernel-latest = callTest tests/kernel-latest.nix {};
tests.kernel-lts = callTest tests/kernel-lts.nix {};
kubernetes: fix minor issues
2017-05-24 20:05:54 +03:00
tests.kubernetes = hydraJob (import tests/kubernetes/default.nix { system = "x86_64-linux"; });
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.latestKernel.login = callTest tests/login.nix { latestKernel = true; };
nixos/tests: add tests for the LDAP stack
2017-05-26 22:42:24 +03:00
tests.ldap = callTest tests/ldap.nix {};
Disable lightdm test It's hanging in the OCR step for hours. @aszlig http://hydra.nixos.org/build/24268601
2015-08-17 11:48:04 +03:00
#tests.lightdm = callTest tests/lightdm.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.login = callTest tests/login.nix {};
Disable the logstash test It's broken because it uses the "grep" plugin, which is no longer included in the standard distribution.
2014-09-05 17:28:55 +04:00
#tests.logstash = callTest tests/logstash.nix {};
nixos/mathics: New service and test
2015-09-08 10:17:21 +03:00
tests.mathics = callTest tests/mathics.nix {};
nixos/tests: add matrix-synapse test
2017-11-04 21:21:55 +03:00
tests.matrix-synapse = callTest tests/matrix-synapse.nix {};
release.nix: add mesos test back This is working now again
2017-09-28 15:25:17 +03:00
tests.mesos = callTest tests/mesos.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.misc = callTest tests/misc.nix {};
mongodb service: add test case
2016-09-13 18:38:45 +03:00
tests.mongodb = callTest tests/mongodb.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.mumble = callTest tests/mumble.nix {};
tests.munin = callTest tests/munin.nix {};
nixos/release: include mutableUsers test to release tests.
2017-11-19 21:20:50 +03:00
tests.mutableUsers = callTest tests/mutable-users.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.mysql = callTest tests/mysql.nix {};
mysqlBackup service: let it work with default settings * Grants enough privileges to the configured user so that it can run mysqldump. * Adds a nixos test. * Use systemd timers instead of a cronjob (by @fadenb). * Creates a new user for backups by default, instead of using mysql user. * Ensures that backup user has write permissions on backup location. * Write backup to a temporary file before renaming so that a failed backup won't overwrite the previous backup, and so that the backup location will never contain a partial backup. Breaking changes: * Renamed period to calendar to reflect the change in how to configure the backup time. * A failed backup will no longer result in cron sending an e-mail -- users' monitoring systems must be updated. Resolves #24728
2017-09-23 17:58:07 +03:00
tests.mysqlBackup = callTest tests/mysql-backup.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.mysqlReplication = callTest tests/mysql-replication.nix {};
nixos/tests/nat: Add tests for standalone and firewall based nat
2014-09-19 00:34:29 +04:00
tests.nat.firewall = callTest tests/nat.nix { withFirewall = true; };
nixos/tests/nat: add test for conntrack helper autoloading
2017-01-22 21:42:59 +03:00
tests.nat.firewall-conntrack = callTest tests/nat.nix { withFirewall = true; withConntrackHelpers = true; };
nixos/tests/nat: Add tests for standalone and firewall based nat
2014-09-19 00:34:29 +04:00
tests.nat.standalone = callTest tests/nat.nix { withFirewall = false; };
netdata service: fix permissions for apps.plugin apps.plugin requires capabilities for full process monitoring. with 1.9.0, netdata allows multiple directories to search for plugins and the setuid directory can be specified here. the module is backwards compatible with older configs. a test is included that verifies data gathering for the elevated privileges. one additional attribute is added to make configuration more generic than including configuration in string form.
2017-10-18 02:51:41 +03:00
tests.netdata = callTest tests/netdata.nix { };
nixos/release: Use callSubTests for subtests Should clean up a lot of these redundant lines for various sub-tests. Note that the tests.boot* are now called tests.boot.boot*, but otherwise all the test attribute names should stay the same. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra Cc: @wkennington Cc: @bobvanderlinden
2016-02-29 22:11:04 +03:00
tests.networking.networkd = callSubTests tests/networking.nix { networkd = true; };
tests.networking.scripted = callSubTests tests/networking.nix { networkd = false; };
nixos/tests: add networking-proxy.nix to release
2014-11-30 17:22:12 +03:00
# TODO: put in networking.nix after the test becomes more complete
tests.networkingProxy = callTest tests/networking-proxy.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.nfs3 = callTest tests/nfs.nix { version = 3; };
Add nfs4 test
2015-04-02 18:44:48 +03:00
tests.nfs4 = callTest tests/nfs.nix { version = 4; };
nixos: enable nginx test cc #23279
2017-03-20 21:05:22 +03:00
tests.nginx = callTest tests/nginx.nix { };
nixos/nghttpx: add module for the nghttpx proxy server (#31680) * nghttpx: Add a new NixOS module for the nghttpx proxy server This change also adds a global `uid` and `gid` for a `nghttpx` user and group as well as an integration test. * nixos/nghttpx: fix building manual
2017-11-16 21:21:02 +03:00
tests.nghttpx = callTest tests/nghttpx.nix { };
release: only run novacomd test on x86_64-linux novacom and novacomd build on aarch64, but the daemon fails to start with something like: novacomd[547]: unhandled level 2 translation fault (11) at 0x00000000, esr 0x92000046 So, uh, nevermind that then.
2018-02-20 22:46:10 +03:00
tests.novacomd = callTestOnTheseSystems ["x86_64-linux"] tests/novacomd.nix { };
leaps: 0.5.1 + add a service + test
2016-11-06 12:33:21 +03:00
tests.leaps = callTest tests/leaps.nix { };
nixos/tests: Add basic test for nsd module. Currently only tests basic resource record lookup against IPv4 and IPv6. Nothing special yet, but probably enough for most setups. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-09-05 04:52:05 +04:00
tests.nsd = callTest tests/nsd.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.openssh = callTest tests/openssh.nix {};
owncloud: fix some but not all errors * Don't set timezone when it's null * Don't create the postgres role because the postgresqsl service already does that. * Fix documentation * Add a test suite
2017-10-31 19:53:49 +03:00
tests.owncloud = callTest tests/owncloud.nix {};
pam_oath: require OATH and pam_unix credentials to be valid
2017-02-13 02:17:08 +03:00
tests.pam-oath-login = callTest tests/pam-oath-login.nix {};
nixos/release.nix: More refactoring for multi-arch Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you end up with e.g. `nixos.tests.docker` which actually silently runs on x86_64-linux. Using the new callTestOnTheseSystems fixes that. As a side-effect, this also causes a rename of `nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO a good thing since it's makes them consistent with the rest of the tests.
2018-01-11 19:16:17 +03:00
#tests.panamax = callTestOnTheseSystems ["x86_64-linux"] tests/panamax.nix {};
nixos/peerflix: add test to release.nix
2014-12-01 18:45:38 +03:00
tests.peerflix = callTest tests/peerflix.nix {};
php: Add nixos test to ensure php-pcre works in httpd
2017-11-12 10:05:27 +03:00
tests.php-pcre = callTest tests/php-pcre.nix {};
test all postgresql versions, test server restart (#1735)
2017-02-11 07:57:57 +03:00
tests.postgresql = callSubTests tests/postgresql.nix {};
postage: replaced by pgmanage-10.0.2 postage is no longer maintained and has been replaced by the identical pgmanage. See: https://github.com/workflowproducts/postage#postage-has-been-replaced-with-pgmanage The following error is raised when a user enables the deprecated `services.postage.enable` option: Failed assertions: - services.postage is deprecated in favor of pgmanage. They have the same options so just substitute postage for pgmanage.
2017-11-02 22:35:05 +03:00
tests.pgmanage = callTest tests/pgmanage.nix {};
postgis: add v2.4.0 Add postgis 2.4.0 doesn't remove v2.3.1. There are some big change in 2.4 that people may don't want. see https://postgis.net/docs/release_notes.html#idm41021 fix test call modify following recommandation of lsix
2017-10-11 19:06:20 +03:00
tests.postgis = callTest tests/postgis.nix {};
nixos/powerdns: add test
2018-02-17 16:36:28 +03:00
tests.powerdns = callTest tests/powerdns.nix {};
treewide: mark a bunch of failing builds as broken (cherry picked from commit 23fdbaa37599f490435056b9865023870656571b) [dezgeg: Un-mark shotcut, tokei & uchiwa that do build on master]
2017-09-29 00:16:18 +03:00
#tests.pgjwt = callTest tests/pgjwt.nix {};
nixos/tests: add predictable-interface-names.nix (#34305)
2018-02-09 21:40:39 +03:00
tests.predictable-interface-names = callSubTests tests/predictable-interface-names.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.printing = callTest tests/printing.nix {};
nixos/tests: enable prometheus test As far as I can tell, we've had this test since 2015, but it was never enabled.
2017-10-16 20:36:13 +03:00
tests.prometheus = callTest tests/prometheus.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.proxy = callTest tests/proxy.nix {};
nixos tests: pump.io: init
2015-11-30 21:19:42 +03:00
tests.pumpio = callTest tests/pump.io.nix {};
quagga service: disable
2017-03-30 13:29:20 +03:00
# tests.quagga = callTest tests/quagga.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.quake3 = callTest tests/quake3.nix {};
radicale: 1.1.4 -> 2.1.2 This commit readds and updates the 1.x package from 1.1.4 to 1.1.6 which also includes the needed command for migrating to 2.x The module is adjusted to the version change, defaulting to radicale2 if stateVersion >= 17.09 and radicale1 otherwise. It also now uses ExecStart instead of the script service attribute. Some missing dots at the end of sentences were also added. I added a paragraph in the release notes on how to update to a newer version.
2017-07-25 10:01:08 +03:00
tests.radicale = callTest tests/radicale.nix {};
nixos/tests: add basic tests for services.rspamd
2018-02-02 03:35:32 +03:00
tests.rspamd = callSubTests tests/rspamd.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.runInMachine = callTest tests/run-in-machine.nix {};
nixos/rdma-core: add module for soft RoCE and test (#34607)
2018-02-10 10:52:03 +03:00
tests.rxe = callTest tests/rxe.nix {};
Add a simple test for Samba
2016-09-30 22:24:18 +03:00
tests.samba = callTest tests/samba.nix {};
nixos/sddm: test automatic and manual login
2017-03-24 18:38:16 +03:00
tests.sddm = callSubTests tests/sddm.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.simple = callTest tests/simple.nix {};
nixos: Add a VM test for the SLiM display manager This is currently our default display manager, so I'm adding this to the "tested" job as well to ensure we don't ship broken revisions where X is most likely not working. The test uses a custom SLiM theme that's specifically tailored for good OCR results (mainly white background and black fonts without anything else), because our default NixOS theme has a very small contrast between background and fonts in some places. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2017-04-23 20:14:44 +03:00
tests.slim = callTest tests/slim.nix {};
smokeping: init at 2.6.11 (#17090) Includes a module for service setup and a test to verify functionality of both service and pkg.
2016-07-21 02:07:59 +03:00
tests.smokeping = callTest tests/smokeping.nix {};
snapper: add nixos module fixes #27154
2017-07-05 17:19:32 +03:00
tests.snapper = callTest tests/snapper.nix {};
services.statsd: add simple test
2017-11-26 03:15:10 +03:00
tests.statsd = callTest tests/statsd.nix {};
sudo: define extra rules in Nix language (#33905)
2018-01-17 17:56:08 +03:00
tests.sudo = callTest tests/sudo.nix {};
nixos/release: add nixos/tests/switch-test.nix to tested job
2017-11-19 21:50:08 +03:00
tests.switchTest = callTest tests/switch-test.nix {};
nixos/tests: Add a test for the Taskserver service A small test which checks whether tasks can be synced using the Taskserver. It doesn't test group functionality because I suspect that they're not yet implemented upstream. I haven't done an in-depth check on that but I couldn't find a method of linking groups to users yet so I guess this will get in with one of the text releases of Taskwarrior/Taskserver. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2016-04-05 18:52:55 +03:00
tests.taskserver = callTest tests/taskserver.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.tomcat = callTest tests/tomcat.nix {};
Add a test for udisks2
2014-04-19 16:37:05 +04:00
tests.udisks2 = callTest tests/udisks2.nix {};
vault: add nixos test
2017-12-04 14:42:30 +03:00
tests.vault = callTest tests/vault.nix {};
nixos/release.nix: Introduce callSubTestsOnTheseSystems The existing callSubTests seems to already have special-cased code to allow enabling subtests on a single specific system by looking at the `system` attribute in the test arguments. Replace it with a new version similar to the callTestOnTheseSystems because: - It's consistent with the existing functions for creating system-specific tests (though admittedly, the callSubTests special case for `system` predates them) - This approach allows limiting to multiple system types, the previous one inherently allows only one system type. - This also fixes the problem that if you pass in e.g. supportedSystems = [ "aarch64-linux" ], you end up with a tests.chromium job that silently runs on x86_64-linux. - Finally, this causes renames of the jobs like: tests.chromium -> tests.chromium.x86_64-linux to be consistent with the rest of the tests.
2018-01-23 00:19:06 +03:00
tests.virtualbox = callSubTestsOnTheseSystems ["x86_64-linux"] tests/virtualbox.nix {};
nixos/release.nix: added tests.wordpress
2017-03-18 13:10:49 +03:00
tests.wordpress = callTest tests/wordpress.nix {};
Make it easier to run the tests You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
2014-04-14 16:02:44 +04:00
tests.xfce = callTest tests/xfce.nix {};
Add XMonad test
2017-09-04 21:03:20 +03:00
tests.xmonad = callTest tests/xmonad.nix {};
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 03:14:00 +03:00
tests.yabar = callTest tests/yabar.nix {};
zookeeper: Add simple test
2017-11-02 20:59:10 +03:00
tests.zookeeper = callTest tests/zookeeper.nix {};
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
/* Build a bunch of typical closures so that Hydra can keep track of
the evolution of closure sizes. */
closures = {
smallContainer = makeClosure ({ pkgs, ... }:
{ boot.isContainer = true;
services.openssh.enable = true;
});
tinyContainer = makeClosure ({ pkgs, ... }:
{ boot.isContainer = true;
imports = [ modules/profiles/minimal.nix ];
});
ec2 = makeClosure ({ pkgs, ... }:
{ imports = [ modules/virtualisation/amazon-image.nix ];
});
kde = makeClosure ({ pkgs, ... }:
{ services.xserver.enable = true;
nixos: update default cases from KDM/KDE4 to SDDM/KDE5
2017-02-10 05:25:03 +03:00
services.xserver.displayManager.sddm.enable = true;
nixos: fix renaming warning in KDE closure
2017-03-03 16:24:58 +03:00
services.xserver.desktopManager.plasma5.enable = true;
Build a few NixOS system closures on Hydra This will allow us to keep track of the evolution of closure sizes of some typical configurations. (Hydra stores closure sizes in its database.)
2014-08-22 13:37:31 +04:00
});
xfce = makeClosure ({ pkgs, ... }:
{ services.xserver.enable = true;
services.xserver.desktopManager.xfce.enable = true;
});
# Linux/Apache/PostgreSQL/PHP stack.
lapp = makeClosure ({ pkgs, ... }:
{ services.httpd.enable = true;
services.httpd.adminAddr = "foo@example.org";
services.postgresql.enable = true;
services.postgresql.package = pkgs.postgresql93;
environment.systemPackages = [ pkgs.php ];
});
};
Add an aggregated to replace the "tested" NixOS view Also get rid of the "system" jobset input.
2013-03-26 17:00:31 +04:00
}
Reference in New Issue Copy Permalink