hydra/src/Hydra/root/releasesets.tt

[% WRAPPER layout.tt title="Release Sets" %]
[% PROCESS common.tt %]

<h1>Release Sets</h1>

<p>Project <tt>[% curProject.name %]</tt> has the following release sets:</p>

<ul>
  [% FOREACH releaseSet IN releaseSets %]
    <li>
      <a href="[% c.uri_for('/releases' curProject.name releaseSet.name) %]"><tt>[% releaseSet.name %]</tt></a>
      (<a href="[% c.uri_for('/releases' curProject.name releaseSet.name "edit") %]">edit</a>)
    </li>
  [% END %]
</ul>

[% END %]
* Basic release management: releases are now dynamically computed as database queries from a set of jobs that have to be in a release. E.g. a patchelf release might consist of the jobs "tarball", "build", and "rpm_fedora10i386". Here the first job ("tarball") is the primary job: all the others have it as an input. The primary job supplies the identity of the release. 2008-11-27 15:16:06 +00:00			`[% WRAPPER layout.tt title="Release Sets" %]`
			`[% PROCESS common.tt %]`

			`<h1>Release Sets</h1>`

			`<p>Project <tt>[% curProject.name %]</tt> has the following release sets:</p>`

			`<ul>`
			`[% FOREACH releaseSet IN releaseSets %]`
2008-11-27 21:08:17 +00:00			`<li>`
			`<a href="[% c.uri_for('/releases' curProject.name releaseSet.name) %]"><tt>[% releaseSet.name %]</tt></a>`
			`(<a href="[% c.uri_for('/releases' curProject.name releaseSet.name "edit") %]">edit</a>)`
			`</li>`
* Basic release management: releases are now dynamically computed as database queries from a set of jobs that have to be in a release. E.g. a patchelf release might consist of the jobs "tarball", "build", and "rpm_fedora10i386". Here the first job ("tarball") is the primary job: all the others have it as an input. The primary job supplies the identity of the release. 2008-11-27 15:16:06 +00:00			`[% END %]`
			`</ul>`

			`[% END %]`