Hydra, the Nix-based continuous build system

Eelco Dolstra 018585dba8 * In the job status page and the channels, pick the build with the ... highest ID rather than the highest timestamp. Otherwise, if a build from revision N finishes after a build from revision N + 1, then the build from revision N will end up in the channel. Thus, the channel contents will be out of sync. This is still not quite correct: if a revision *reverts* to an older build, the channel will still end up out of sync, because Hydra won't schedule the build again (after all, it has already done it). A better fix would be to add a separate timestamp denoting when the build was last "current" (i.e. corresponding to the "head revision" of its job).		2009-04-22 13:55:20 +00:00
doc/manual	why nix is covered in intro	2008-12-01 23:23:01 +00:00
src	* In the job status page and the channels, pick the build with the	2009-04-22 13:55:20 +00:00
COPYING	* Include a license.	2008-11-28 11:18:29 +00:00
release.nix	* perl -> perlPackages.	2009-04-20 12:51:47 +00:00