ahuston-0/hydra
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity
hydra/src/root/jobset-channels-tab.tt

35 lines
1.1 KiB
Plaintext
Raw Normal View History

jobset: Add a new "channels" tab. It's very similar to "jobs" and the code is pretty much the same, except that we don't do filtering on it. At least it doesn't waste space for a filter option when there are usually WAY less channel jobs than ordinary jobs. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-04-14 08:58:55 +02:00
[% PROCESS common.tt %]
[% IF channels.size == 0 %]
Style unstyled alerts
2021-03-31 20:03:44 -04:00
<div class="alert alert-warning">There are no channels available.</div>
jobset: Add a new "channels" tab. It's very similar to "jobs" and the code is pretty much the same, except that we don't do filtering on it. At least it doesn't waste space for a filter option when there are usually WAY less channel jobs than ordinary jobs. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-04-14 08:58:55 +02:00
[% ELSE %]
[% evalIds = evals.keys.nsort.reverse %]
<table class="table table-striped table-condensed table-header-rotated">
<thead>
<tr>
<th style="width: 1em;">Channel</th>
[% FOREACH eval IN evalIds %]
<th class="rotate-45">
<div><span>
<a href="[% c.uri_for('/eval' eval) %]">[% INCLUDE renderRelativeDate timestamp=evals.$eval.timestamp %]</a>
</span></div></th>
[% END %]
</tr>
</thead>
<tbody>
[% FOREACH chan IN channels-%]
<tr>
Tie custom channels into channel-contents.tt. We should now get an overview and help text on how to add a particular channel and also a bit of information about the builds that are required for a channel to get upgraded. Right now we only select the latest successful build in the latest successful evaluation, so if someone wants to have more information about which channel has failed, (s)he still has to look at the "Channels" tab of the jobset. We can make this more fancy at some later point if this is really needed, because right now we're only interested in the latest build, because it's the only thing necessary to deliver the channel contents. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-04-27 03:03:41 +02:00
<th><span><a href="[% c.uri_for('/channel/custom' project.name jobset.name chan) %]">[% chan %]</a></span></th>
jobset: Add a new "channels" tab. It's very similar to "jobs" and the code is pretty much the same, except that we don't do filtering on it. At least it doesn't waste space for a filter option when there are usually WAY less channel jobs than ordinary jobs. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-04-14 08:58:55 +02:00
[% FOREACH eval IN evalIds %]
Jobset.pm: Factor out build->eval mapping. 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>
2015-04-26 07:37:37 +02:00
<td>[% r = evals.$eval.builds.$chan; IF r.id %]<a href="[% c.uri_for('/build' r.id) %]">[% INCLUDE renderBuildStatusIcon size=16 build=r %]</a>[% END %]</td>
jobset: Add a new "channels" tab. It's very similar to "jobs" and the code is pretty much the same, except that we don't do filtering on it. At least it doesn't waste space for a filter option when there are usually WAY less channel jobs than ordinary jobs. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-04-14 08:58:55 +02:00
[% END %]
</tr>
[% END %]
</tbody>
</table>
[% END %]
Reference in New Issue Copy Permalink