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
..
Base/Controller	* Job status / error pages: show only active jobs.	2009-04-15 14:50:15 +00:00
Controller	* Don't do pretty printing for large logs, because the XSLT processing	2009-04-16 15:22:14 +00:00
Helper	* Big speed-up of the job status page and the channel generation (such	2009-04-03 15:37:21 +00:00
Model	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
Schema	* In the job status page and the channels, pick the build with the	2009-04-22 13:55:20 +00:00
View	* Generate SVG instead of PNG, which is much faster and smaller. I	2009-03-31 15:59:31 +00:00
Schema.pm	* Represent jobs explicitly in the DB.	2009-03-13 14:49:25 +00:00