1
I Use This!
Moderate Activity

Commits : Listings

Analyzed about 9 hours ago. based on code collected about 9 hours ago.
Aug 19, 2024 — Aug 19, 2025
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
* eval-jobs -> hydra_eval_jobs. More... over 16 years ago
* Inputs of type "build" must now be declared explicitly. More... over 16 years ago
* hydra_scheduler: use eval-jobs. More... over 16 years ago
* Require every argument to be specified. More... over 16 years ago
[no comment] More... over 16 years ago
* Report evaluation errors per job, and don't bail out if a job fails to evaluate. More... over 16 years ago
* eval-jobs now efficiently evaluates all Hydra jobs from a release.nix expression, accepting multiple values for function arguments. This is much faster than calling nix-instantiate / nix-env a zillion times (which is particularly important for Nixpkgs). More... over 16 years ago
* Export all relevant info about the derivation. More... over 16 years ago
* Export all relevant info about the derivation. More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
* For products that are directories (like manuals), allow a default suffix other than index.html to be declared. E.g. if a build does More... over 16 years ago
* Allow scheduled builds to be cancelled. They're not removed from the database, just marked as cancelled, because otherwise the scheduler would just add them again. More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
* Start of a helper tool to evaluate job expressions efficiently. More... over 16 years ago
[no comment] More... over 16 years ago
* Move everything up one directory. More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
* Controller for jobs which inherits all actions in ListBuilds. So for instance we get channels specific for each job. More... over 16 years ago
* At top-level and for each project, provide two channels: "latest" (containing the latest successful build of each job) and "all" (containing all successful builds ever). More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
[no comment] More... over 16 years ago
* XHTML validity. More... over 16 years ago
* Channels: provide an index page that lists all the packages in the channel. * Store the meta.homepage attribute in the Builds table. More... over 16 years ago
* Provide a channel for each project containing all the latest succesful builds for each job in the project (under http://server/project/<name>/channel/latest). More... over 16 years ago