Eelco Dolstra 2755c895ff * In job inputs of type "build", allow the project and jobset names of ... the input build to be specified, as well as constraints on the inputs of the inputs build. For instance, you can require that a build has input `system = "i686-linux"'. This is important when one binary build serves as an input to another binary build. Obviously, we shouldn't pass a build on i686-linux as an input to another on i686-darwin. Hence the necessity for constraint. The constraint are currently quite limited. What you really want to say is that the "system" input of the other build has to match the "system" input of this build. But those require a bit more work since they introduce dependencies between inputs.		2009-03-20 14:50:09 +00:00
..
hydra_build.pl	* Doh.	2009-03-16 17:46:46 +00:00
hydra_cgi.pl	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
hydra_control.sh	* Remove redundant -fork.	2009-03-11 15:52:39 +00:00
hydra_create.pl	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
hydra_fastcgi.pl	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
hydra_init.pl	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
hydra_queue_runner.pl		2009-03-16 17:51:42 +00:00
hydra_scheduler.pl	* In job inputs of type "build", allow the project and jobset names of	2009-03-20 14:50:09 +00:00
hydra_server.pl	* Use Catalyst's HTTP::Prefork engine by default, with some limits to	2009-03-11 15:48:06 +00:00
hydra_test.pl	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
hydra_update_gc_roots.pl	* Register GC roots properly.	2009-03-15 11:56:11 +00:00