> -----Original Message----- > From: Adam R. B. Jack [mailto:[EMAIL PROTECTED] > Sent: 03 December 2003 18:33 > To: Gump code and data > Subject: Re: Gump dates and times (Was Re: junit reports output) > > > > 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.
Thanks. > > > 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. Thanks again. I was thinking maybe there could be an option to specify the timezone (stored in a cookie?), and have the times converted on the fly... > > > 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? Yes, that's what I mean. > 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? Because the time between the end of one build and the start of the next CVS is reduced. If CVS is done just before the build, then the amount of time available to get a fix into CVS is roughly 24 hours, assuming one build per day and a few minutes to do the CVS and build. With the current process, the CVS extract for the first project in the list will be in 24 hours *minus* the total CVS job time, and for the last project it will be in 24 hours *minus* the build time for all the other projects, assuming that the CVS order is the same as the build order. == Also, if I know that my project has just been built, I don't know whether the CVS commit I submitted an hour or two ago will be included or not without looking at the CVS fetch time. Whereas, if the build immediately followed CVS, one would only need to check the times for very recent checkins. This could be made easier to check by including the CVS times in the Project log. > > I've tried added the time of the CVS update to the build log. Thanks. S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
