about summary refs log tree commit diff
path: root/tests/build-hook.hook.sh
AgeCommit message (Collapse)AuthorFilesLines
2010-06-25 tests/build-hook.hook.sh: prefer more portable `...` syntax over $(...) for ↵Peter Simons1-2/+2
running sub-shells The /bin/sh interpreter on Solaris doesn't understand $(...) syntax for running sub-shells. Consequently, this test fails on Solaris. To remedy the situation, the script either needs to be run by /bin/bash -- which is non-standard --, or it needs to use the ancient but portable `...` syntax.
2009-03-28 * Simplify communication with the hook a bit (don't use fileEelco Dolstra1-3/+3
descriptors 3/4, just use stdin/stderr).
2005-01-25 * Fix the build hook mechanism; pass the pointer graph to the hook.Eelco Dolstra1-2/+2
2004-05-13 * Set the executable bit.Eelco Dolstra1-0/+0
2004-05-13 * The build hooks used to implement distributed builds can now be runEelco Dolstra1-6/+10
in parallel. Hooks are more efficient: locks on output paths are only acquired when the hook says that it is willing to accept a build job. Hooks now work in two phases. First, they should first tell Nix whether they are willing to accept a job. Nix guarantuees that no two hooks will ever be in the first phase at the same time (this simplifies the implementation of hooks, since they don't have to perform locking (?)). Second, if they accept a job, they are then responsible for building it (on the remote system), and copying the result back. These can be run in parallel with other hooks and locally executed jobs. The implementation is a bit messy right now, though. * The directory `distributed' shows a (hacky) example of a hook that distributes build jobs over a set of machines listed in a configuration file.
2004-05-12 * An quick and dirty hack to support distributed builds.Eelco Dolstra1-0/+17