* Give releases a timestamp.

Dependencies

• [2] JFZNAYJX * Showing releases.
• [3] FHF6IZJQ * Basic release management: releases are now dynamically computed as
• [4] 5ZHSCNLJ
• [5] RU7AQO7U * Role-based access control. Only admins can create projects. Only
• [*] J5UVLXOK * Start of a basic Catalyst web interface.
• [*] N22GPKYT * Put info about logs / build products in the DB.

Change contents

• edit in src/Hydra/lib/Hydra/Controller/Root.pm at line 231
  [2.589]

  [2.589]
  +

  + # The timestamp of the release is the highest timestamp of all

  + # constitutent builds.

  + my $timestamp = 0;
• edit in src/Hydra/lib/Hydra/Controller/Root.pm at line 260
  [2.1556]

  [2.1556]
  +

  + $timestamp = $thisBuild->timestamp

  + if defined $thisBuild && $thisBuild->timestamp > $timestamp;
• edit in src/Hydra/lib/Hydra/Controller/Root.pm at line 272
  [2.1787]

  [2.1787]
  + , timestamp => $timestamp
• edit in src/Hydra/root/releases.tt at line 15
  [3.8698]

  [3.8698]
  + <th>Date</th>
• edit in src/Hydra/root/releases.tt at line 43
  [3.9509]

  [3.9509]
  + <td>[% INCLUDE renderDateTime timestamp=release.timestamp %]</td>
• replacement in src/Hydra/sql/hydra.sql at line 300
  [3.11598]→[3.11598:11909](∅→∅)
  − -- multiple builds matching a ReleaseSetJob, then we take the *oldest*

  − -- successful build (for release stability), or the *newest*

  − -- unsuccessful build if there is no succesful build. A release is

  − -- itself considered successful if all builds (except those for jobs

  − -- that have mayFail set) are successful.
  [3.11598]

  [3.11909]
  + -- multiple builds matching a ReleaseSetJob, then we take the oldest

  + -- successful build, or the oldest unsuccessful build if there is no

  + -- successful build. A release is itself considered successful if all

  + -- builds (except those for jobs that have mayFail set) are

  + -- successful.