about summary refs log tree commit diff
path: root/scripts
AgeCommit message (Collapse)AuthorFilesLines
2010-02-04 * Revert r19796 for now.Eelco Dolstra1-1/+1
2010-02-03 * Respect @sysconfdir@.Eelco Dolstra1-1/+1
2010-02-03 * In the build hook, if connecting to a machine fails, try the otherEelco Dolstra3-73/+77
machines of the right type (if available). This makes the build farm more robust to failures.
2010-02-03 * Use SSH connection sharing in the remote build script.Eelco Dolstra1-36/+16
* Removed the Cygwin password hack since the problem is apparently fixed in Visual Studio.
2010-02-03 * nix-copy-closure: start only one SSH connection to the server, orEelco Dolstra3-5/+49
recycle an already existing connection (using OpenSSH's connection sharing feature).
2010-02-02 * Don't do a chdir to $tmpDir. It's not necessary, and Windows doesn'tEelco Dolstra1-2/+0
support deleting the current directory.
2010-01-25 * Disable gzip compression in build-remote.pl because it puts too muchEelco Dolstra1-2/+2
load on the Hydra build farm (where it's unnecessary anyway because it has a fast connection to the build machines). In any case, compression can be enabled by using the `-C' option to ssh.
2009-12-09 * When doing a nix-pull, remove old manifests downloaded from the sameEelco Dolstra2-8/+23
URL. This prevents lots of old cruft accumulating in /nix/var/nix/manifests.
2009-12-09 * nix-build: be less verbose.Eelco Dolstra1-1/+8
2009-11-17 * Don't pass -K. It should really inherit the setting of the callingEelco Dolstra1-1/+1
Nix though.
2009-11-13 * In nix-pull/nix-channel, create the manifests directory if itEelco Dolstra2-0/+9
doesn't exist. The Debian packages don't include the manifests directory, so nix-channel would silently skip doing a nix-pull, resulting in everything being built from source. Thanks to Juan Pedro Bolívar Puente.
2009-09-17 (no commit message)Eelco Dolstra1-0/+1
2009-09-17 * build-remote.pl: Pick machines in a round-robin order, rather thanEelco Dolstra1-23/+67
giving jobs to the first machine until it hits its job limit, then the second machine and so on. This should improve utilisation of the Hydra build farm a lot. Also take an optional speed factor into account to cause fast machines to be preferred over slower machines with a similar load.
2009-09-17 * build-remote.pl: allow the system type to be a comma-separated listEelco Dolstra1-5/+4
of system types. Don't treat the x86_64-linux system type specially.
2009-07-15 * nix-build: pass the --show-trace flag.Eelco Dolstra1-0/+4
2009-06-10 * nix-build: if nix-instantiate or nix-store fails due to a signalEelco Dolstra1-2/+8
(e.g. out of memory or a segfault), print an error message. Otherwise the user doesn't see anything.
2009-04-21 * Machines of type x86_64-linux can do i686-linux builds.Eelco Dolstra1-1/+3
2009-04-16 * Cleanup.Eelco Dolstra1-15/+6
2009-03-29 * Update the mtime on the lock file to make it easy to see when a slotEelco Dolstra1-4/+8
was last used.
2009-03-29 * Use polling to wait for a remote build slot when using a build hookEelco Dolstra1-5/+2
(that is, call the build hook with a certain interval until it accepts the build). * build-remote.pl was totally broken: for all system types other than the local system type, it would send all builds to the *first* machine of the appropriate type.
2009-03-28 * nix-copy-closure: compute the closure in one call to nix-store,Eelco Dolstra2-26/+10
which is much faster.
2009-03-28 * Simplify communication with the hook a bit (don't use fileEelco Dolstra1-7/+2
descriptors 3/4, just use stdin/stderr).
2009-03-28 * Clean up the output a bit.Eelco Dolstra1-5/+5
2009-03-19 * Future proofing: assume we can read manifests up to version 10Eelco Dolstra1-1/+6
(which should therefore be backwards compatible).
2009-03-19 * Disregard the Hash field in manifests.Eelco Dolstra1-22/+5
2009-03-18 * Unify exportReferencesGraph and exportBuildReferencesGraph, and makeEelco Dolstra1-5/+1
sure that it works as expected when you pass it a derivation. That is, we have to make sure that all build-time dependencies are built, and that they are all in the input closure (otherwise remote builds might fail, for example). This is ensured at instantiation time by adding all derivations and their sources to inputDrvs and inputSrcs.
2009-03-18 * Clean up some tests (use nix-build where appropriate).Eelco Dolstra1-1/+8
2009-02-27 * nix-install-package: don't pollute /nix/var/nix/manifests.Eelco Dolstra3-11/+11
2009-02-27 * Use the regular progress bar; the hash bar isn't very useful whenEelco Dolstra1-1/+1
the size of the download isn't known in advance.
2009-02-27 * nix-build: support --option.Eelco Dolstra1-0/+7
2009-02-27 * nix-channel: use nix-build.Eelco Dolstra1-8/+6
2009-02-27 * Check the manifest version.Eelco Dolstra1-3/+4
2009-02-26 * Handle base-16 hashes in manifests.Eelco Dolstra1-1/+12
2009-02-19 * download-using-manifests: don't check the cryptographic hash ofEelco Dolstra1-18/+30
downloaded files; rather, check the hash of the unpacked store path. When the server produces bzipped NAR archives on demand (like Hydra does), the hash of the file is not known in advance; it's streamed from the server. Thus the manifest doesn't contain a hash for the bzipped NAR archive. However, the server does know the hash of the *uncompressed* NAR archive (the "NarHash" field), since it's stored in the Nix database (nix-store -q --hash /nix/store/bla). So we use that instead for checking the integrity of the download.
2009-02-19 Replace wrong (w.r.t. PATH) sed call with in-shell substitutionMichael Raskin1-1/+2
2009-02-03 * Build hook: compress the transferred data.Eelco Dolstra1-2/+2
2009-02-02 * Build hooks: use nix-store --import. This prevents a redundantEelco Dolstra1-13/+2
scan for runtime dependencies (i.e. the local machine shouldn't do a scan that the remote machine has already done). Also pipe directly into `nix-store --import': don't use a temporary file.
2009-01-13 * When using a build hook, distinguish between transient failuresEelco Dolstra1-2/+10
(e.g. an SSH connection problem) and permanent failures (i.e. the builder failed). This matters to Hydra (it wants to know whether it makes sense to retry a build).
2009-01-13 (no commit message)Eelco Dolstra1-1/+1
2008-12-04 (no commit message)Eelco Dolstra1-2/+1
2008-12-04 * Propagate --max-silent-time to remote machines.Eelco Dolstra1-2/+6
2008-12-04 * Prefer building on a remote machine over a local machine. ThisEelco Dolstra1-5/+6
makes more sense for the build farm, otherwise every nix-store invocation will lead to at least one local build. Will come up with a better solution later...
2008-12-04 * When using build hooks, for any nix-store -r build operation, it isEelco Dolstra1-6/+6
necessary that at least one build hook doesn't return "postpone", otherwise nix-store will barf ("waiting for a build slot, yet there are no running children"). So inform the build hook when this is the case, so that it can start a build even when that would exceed the maximum load on a machine.
2008-12-04 * Force allocation of a pseudo-terminal to clean up the remoteEelco Dolstra1-1/+6
nix-store process when the connection is interrupted.
2008-12-04 * Support multiple system types per remote machine, e.g. a machineEelco Dolstra1-24/+24
list like root@example.org x86_64-linux /root/.ssh/id_buildfarm 1 root@example.org i686-darwin /root/.ssh/id_buildfarm 1 This is possible when the Nix installation on example.org itself has remote builds enabled.
2008-12-04 * Dirty hack to make nix-push work properly on derivations: theEelco Dolstra1-2/+1
derivation should be a source rather than a derivation dependency of the call to the NAR derivation. Otherwise the derivation (and all its dependencies) will be built as a side-effect, which may not even succeed.
2008-11-20 (no commit message)Eelco Dolstra1-1/+8
2008-11-20 * Urgh.Eelco Dolstra8-21/+29
2008-11-19 * Primop builtins.storePath for declaring a store path as aEelco Dolstra1-1/+1
dependency. `storePath /nix/store/bla' gives exactly the same result as `toPath /nix/store/bla', except that the former includes /nix/store/bla in the dependency context of the string. Useful in some generated Nix expressions like nix-push, which now finally does the right thing wrt distributed builds. (Previously the path to be packed wasn't an explicit dependency, so it wouldn't be copied to the remote machine.)
2008-11-18 * Get rid of nix-pack-closure / nix-unpack-closure, they're redundant.Eelco Dolstra3-165/+0