From 8fdd156a650f9b2ce9ae8cd74edcf16225478292 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 9 Nov 2015 23:16:24 +0100 Subject: Add option to verify build determinism Passing "--option build-repeat " will cause every build to be repeated N times. If the build output differs between any round, the build is rejected, and the output paths are not registered as valid. This is primarily useful to verify build determinism. (We already had a --check option to repeat a previously succeeded build. However, with --check, non-deterministic builds are registered in the DB. Preventing that is useful for Hydra to ensure that non-deterministic builds don't end up getting published at all.) --- doc/manual/command-ref/conf-file.xml | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc/manual/command-ref') diff --git a/doc/manual/command-ref/conf-file.xml b/doc/manual/command-ref/conf-file.xml index c947d19fa0e1..71a34950901c 100644 --- a/doc/manual/command-ref/conf-file.xml +++ b/doc/manual/command-ref/conf-file.xml @@ -616,6 +616,18 @@ flag, e.g. --option gc-keep-outputs false. + build-repeat + + How many times to repeat builds to check whether + they are deterministic. The default value is 0. If the value is + non-zero, every build is repeated the specified number of + times. If the contents of any of the runs differs from the + previous ones, the build is rejected and the resulting store paths + are not registered as “valid” in Nix’s database. + + + + -- cgit 1.4.1