Eelco Dolstra
3e5e49debd
* Allow a view result to be saved as a release.
2009-10-27 15:31:26 +00:00
Eelco Dolstra
9aa70716ad
2009-10-26 17:03:48 +00:00
Eelco Dolstra
e25f112b82
* Implemented the clone feature.
2009-10-26 17:01:23 +00:00
Eelco Dolstra
e1373fa1c3
* Refactoring: move fetchInput out of hydra_scheduler into a separate
...
module, since Controller/Build.pm needs it to create a new build.
2009-10-26 15:39:14 +00:00
Eelco Dolstra
57cc6ceca6
* UI for cloning builds (not functional yet).
2009-10-26 14:30:42 +00:00
Eelco Dolstra
cb2493eca9
* Store the jobset's nixExprPath and nixExprInput fields in a build to
...
allow it to be cloned (re-executed with modified inputs) later and
to provide some traceability.
2009-10-26 13:33:48 +00:00
Eelco Dolstra
1038e2ebee
* Allow the description of a release member to be edited, and to
...
delete a release member.
2009-10-26 12:04:12 +00:00
Eelco Dolstra
578e37d55c
* Only non-garbage collected builds can be added to a release.
2009-10-26 10:46:57 +00:00
Eelco Dolstra
f984eed77b
* Align the apply/delete buttons.
2009-10-26 10:35:59 +00:00
Eelco Dolstra
7e81fbd56a
* A quick (non-Web 2.0) interface to manually add builds to a release.
2009-10-23 15:57:18 +00:00
Eelco Dolstra
a515c5fef2
2009-10-23 15:05:16 +00:00
Eelco Dolstra
d1bea30cfc
* Editing releases.
2009-10-23 12:42:50 +00:00
Eelco Dolstra
851a4dff4d
* Creating releases.
2009-10-23 09:58:23 +00:00
Eelco Dolstra
929cbe7b7c
* Adding persistant releases. A release is a named set of builds.
2009-10-21 15:44:17 +00:00
Eelco Dolstra
686b6271d2
* Cleaned up the foreign key constraints.
...
* Generate SQLite and PostgreSQL schemas from hydra.sql.
2009-10-21 12:25:43 +00:00
Eelco Dolstra
2cf42489e2
* More renaming.
2009-10-20 12:35:01 +00:00
Eelco Dolstra
321027b262
* More release -> view.
2009-10-20 12:26:39 +00:00
Eelco Dolstra
cec3201720
* Renaming "release sets" to "views" (not finished yet). Having
...
releases as a dynamic view on the database was misguided, since
doing thing like adding a new job to a release set will invalidate
all old releases. So we rename release sets to views, and we'll
reintroduce releases as separate, static entities in the database.
2009-10-15 21:35:19 +00:00
Eelco Dolstra
dd12113eb2
* Pass the page number in the URI query string.
2009-10-15 12:59:55 +00:00
Rob Vermaas
d109910453
* paging for releases page
2009-10-15 11:13:36 +00:00
Eelco Dolstra
903ca3b246
* Make download-by-type more deterministic when there are multiple
...
files of the same type.
2009-10-12 17:07:36 +00:00
Eelco Dolstra
6cedee5476
* Allow jobsets to be disabled.
2009-10-08 11:39:16 +00:00
Eelco Dolstra
08f3b7bf2a
* Use isCurrent to determine the inactive jobs.
2009-10-08 08:54:42 +00:00
Eelco Dolstra
16f2d003b2
* In the last succeeded / job status queries, use the Builds.isCurrent
...
column instead of Jobs.active.
2009-10-07 15:45:17 +00:00
Eelco Dolstra
48d8871dbc
* Only show status changes from successful to failed and failed to
...
successful (not between different kinds of failure).
2009-10-07 13:59:12 +00:00
Eelco Dolstra
7ae263a23a
* Make the queries more readable.
2009-10-07 13:40:58 +00:00
Eelco Dolstra
05c7989c3e
* Don't show platforms that are not included in the current jobset.
2009-10-02 17:11:28 +00:00
Eelco Dolstra
e9cf409d80
* Mark the "current" builds in a jobset, i.e. those corresponding to
...
the derivations that the jobset currently contains. This is
necessary to allow the "latest" channel to contain the correct
builds when the sources of a jobset are reverted.
2009-10-02 16:06:28 +00:00
Eelco Dolstra
2613d8721a
* Don't crawl the channel pages, particularly because the "all"
...
channel can be very large.
2009-09-30 12:26:51 +00:00
Rob Vermaas
d7713b4dba
* Add nix version to footer of hydra pages
2009-09-01 08:50:51 +00:00
Eelco Dolstra
b1289533e6
* More database hackery.
2009-07-09 15:26:55 +00:00
Eelco Dolstra
fa364fa333
* PostgreSQL compatibility.
2009-07-09 15:08:39 +00:00
Eelco Dolstra
1aec78014d
* In the job status and error pages, show when the status of a job
...
last changed.
2009-07-09 14:48:15 +00:00
Eelco Dolstra
5bdd5e7152
* Added a maintainers field to the Builds table.
...
* Regenerated the schema bindings with the latest DBIx::Class.
2009-07-07 13:59:59 +00:00
Eelco Dolstra
3e192cbb90
* Support showing the contents of ISO images (using isoinfo in
...
cdrkit).
2009-07-07 11:37:47 +00:00
Rob Vermaas
1da4f89eae
* added jar to 'contents' list
2009-06-18 13:23:04 +00:00
Rob Vermaas
e457be469c
sequence fix for postgresql
2009-05-11 13:56:52 +00:00
Rob Vermaas
b52796feac
check getHydraPath in stead of Envvar HYDRA_DBI directly
2009-05-09 16:10:50 +00:00
Rob Vermaas
f1611a7edd
check if HYDRA_DBI is defined in stead of empty string comparison
2009-05-09 16:00:08 +00:00
Rob Vermaas
f2a1fb3937
Added sequences for auto increment primary key columns (for PostgreSQL)
2009-05-07 13:30:55 +00:00
Rob Vermaas
a509694220
Hydra now uses an optional HYDRA_DBI environment variable which holds the DBI url. If this variable is not set, sqlite is used like before.
2009-04-29 11:07:46 +00:00
Rob Vermaas
d774cd6f18
changed queries for compatibility with postgresql
2009-04-28 14:21:33 +00:00
Eelco Dolstra
469893cd4a
* The "latest" channel shouldn't contain inactive jobs.
2009-04-25 11:41:46 +00:00
Eelco Dolstra
000fffeb11
2009-04-25 11:27:46 +00:00
Eelco Dolstra
3c47a11bd9
* Don't disable fsync in production.
2009-04-25 07:48:30 +00:00
Eelco Dolstra
97a6011628
* Hack around those SQLite timeouts: just retry the transaction.
2009-04-22 22:43:04 +00:00
Eelco Dolstra
018585dba8
* In the job status page and the channels, pick the build with the
...
highest ID rather than the highest timestamp. Otherwise, if a build
from revision N finishes after a build from revision N + 1, then
the build from revision N will end up in the channel. Thus, the
channel contents will be out of sync.
This is still not quite correct: if a revision *reverts* to an older
build, the channel will still end up out of sync, because Hydra
won't schedule the build again (after all, it has already done it).
A better fix would be to add a separate timestamp denoting when the
build was last "current" (i.e. corresponding to the "head revision"
of its job).
2009-04-22 13:55:20 +00:00
Eelco Dolstra
4d699c97fd
* Don't do pretty printing for large logs, because the XSLT processing
...
is rather slow.
2009-04-16 15:22:14 +00:00
Eelco Dolstra
d6bd9bab5f
* Job status / error pages: show only active jobs.
2009-04-15 14:50:15 +00:00
Eelco Dolstra
2a05522189
* Don't index any of the logs (mostly because xsltproc can be a huge
...
resource hog).
2009-04-14 12:40:00 +00:00