hydra/src/root/jobset-channels-tab.tt

[% PROCESS common.tt %]

[% IF channels.size == 0 %]

  <div class="alert">There are no channels available.</div>

[% 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>
          <th><span>[% INCLUDE renderJobName project=project.name jobset=jobset.name job=chan %]</span></th>
          [% FOREACH eval IN evalIds %]
            <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>
          [% END %]
        </tr>
      [% END %]
    </tbody>
  </table>

[% END %]
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 06:58:55 +00:00			`[% PROCESS common.tt %]`

			`[% IF channels.size == 0 %]`

			`<div class="alert">There are no channels available.</div>`

			`[% 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>`
			`<th><span>[% INCLUDE renderJobName project=project.name jobset=jobset.name job=chan %]</span></th>`
			`[% 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 05:37:37 +00: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 06:58:55 +00:00			`[% END %]`
			`</tr>`
			`[% END %]`
			`</tbody>`
			`</table>`

			`[% END %]`