We now have a searchBuildsAndEvalsForJobset, which creates such a mapping for us, so we don't need to duplicate code in jobs_tab and channels_tab. Also, we're going to use this for the overview of a particular channel as well, so it makes sense to put it in CatalystUtils instead of directly in Jobset.pm. Instead of eval->jobs, it's now eval->builds, because it's really an aggregate over the builds schema, rather than the job schema. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
To start hacking on Hydra, run:
$ ./dev-shell
$ ./configure $configureFlags --prefix=/opt/hydra
$ make
$ make install
Or, if you just want to build from source (on x86_64-linux):
$ nix-build -A build.x86_64-linux release.nix
Description
Languages
Perl
70.5%
C++
15.5%
Nix
6%
PLpgSQL
3%
Shell
2.3%
Other
2.6%