Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm
Message-ID: <164201c3b9cb$e6605b40$9c27fea9@tsws1>
From: "Adam R. B. Jack" <ajack@trysybase.com>
To: "Gump code and data" <gump@jakarta.apache.org>
References: <20031203005621.83743.qmail@web12821.mail.yahoo.com>
 <121801c3b93e$023a1e20$9c27fea9@tsws1>
 <011e01c3b943$69286bf0$3e92b050@EVESHAM>
Subject: Re: Gump dates and times (Was Re: junit reports output)
Date: Wed, 3 Dec 2003 11:33:02 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> The build logs on covalent and cocoon show the start times of each project
in the summary list, whereas the lsd list does not.
> If one is waiting for a build to run, it is useful to be able to scan the
times of builds earlier in the sequence. Any chance of
> that being added to LSD?

 Good point. Added to CVS.

> It would be useful to be able to display the times in GMT (or even better,
local time for the browser), to make it easier to follow
> the sequence of Gump builds.

I've added timezone. I know these big public Gumps could work in GMT, but I
think localtime w/ timezone is best for private ones, so chose that.

> Another suggestion would be to do the CVS fetch just before the build, to
reduce the time-lag between them.
> If there is an error in a build, updates can easily miss the next one or
two CVS runs, reducing turn-round for fixes.

So do CVS/build, CVS/build not CVS/CVS, build,build ? That what you are
saying? I am open minded to the idea, but not sure how it helps what you
suggest. A run takes a finite amount of time, updates occur once a day (or,
at most) once each of those finite times. How does your suggestion help?

I've tried added the time of the CVS update to the build log.

regards

Adam