Eelco Dolstra 8f104396ec Support passing a jobset evaluation as an input ... All successful, non-garbage-collected builds in the evaluation are passed in a attribute set. So if you declare a Hydra input named ‘foo’ of type ‘eval’, you get a set with members ‘foo.<jobname>’. For instance, if you passed a Nixpkgs eval as an input named ‘nixpkgs’, then you could get the Firefox build for x86_64-linux as ‘nixpkgs.firefox.x86_64-linux’. Inputs of type ‘eval’ can be specified in three ways: * As the number of the evaluation. * As a jobset identifier (‘<project>:<jobset>’), which will yield the latest finished evaluation of that jobset. Note that there is no guarantee that any job in that evaluation has succeeded, so it might not be very useful. * As a job identifier (‘<project>:<jobset>:<job>’), which will yield the latest finished evaluation of that jobset in which <job> succeeded. In conjunction with aggregate jobs, this allows you to make sure that the evaluation contains the desired builds.		2013-11-11 21:17:22 +00:00
..
Base/Controller	Handle builds with multiple outputs correctly in Hydra channels	2013-10-07 17:06:17 +02:00
Component	Get rid of old ToJSON code path	2013-10-25 11:09:11 -04:00
Controller	Support passing a jobset evaluation as an input	2013-11-11 21:17:22 +00:00
Helper	Support passing a jobset evaluation as an input	2013-11-11 21:17:22 +00:00
Model	Turn prepared statements back on	2013-02-25 21:20:52 +01:00
Plugin	Remove redundant newlines	2013-10-17 11:20:27 +02:00
Schema	Merge branch 'master' into persona	2013-11-06 12:35:36 +01:00
Script	Use CatalystX::Script::Server::Starman	2011-11-22 16:44:32 +01:00
View	Handle builds with multiple outputs correctly in Hydra channels	2013-10-07 17:06:17 +02:00
Plugin.pm	Pass project and jobset to fetchInput	2013-07-29 15:33:22 -04:00
Schema.pm	Keep track of the database schema version	2011-12-05 14:29:29 +01:00