baec2bbb4c
When using Hydra to build machine configurations, you'll often see "nixosConfigurations.foo" five times, i.e. for each build step being run. This isn't very helpful I think because in such a case, a single build step can also be compiling the Linux kernel. This change also fetches the `drvpath` and `type` from the `buildsteps` relation. We're already joining it, so this doesn't make much difference (confirmed via query logging that this doesn't cause extra SQL queries). Unfortunately build steps don't have a human readable name, so I'm deriving it from the drvpath by stripping away the hash (assuming that it'll never contain a `-` and that `/nix/store/` is used as prefix). I decided against using the Nix bindings for that to avoid too much overhead due to store operations for each build step.
15 lines
311 B
Plaintext
15 lines
311 B
Plaintext
[% WRAPPER layout.tt title="Running builds" %]
|
|
[% PROCESS common.tt %]
|
|
|
|
[% IF resource.size == 0 %]
|
|
|
|
<div class="alert alert-info">There are no running builds.</div>
|
|
|
|
[% ELSE %]
|
|
|
|
[% INCLUDE renderBuildList builds=resource showSchedulingInfo=1 hideResultInfo=1 busy=1 showStepName=1 %]
|
|
|
|
[% END %]
|
|
|
|
[% END %]
|