[Dart] Dashboard rollover times.

[Miller, James V (CRD)]

Brad,

This is what I do to check server changes.  I grab the submitted XML files from public for say VTK.
So I tar up Dashboard/(todays datestamp)/*.xml and Sites/*/*/(todays datestamp)*/XML/*.xml

I then untar this on my local machine (in the right place in one of my builds) and do a "Nightly
DashboardEnd". Tarring up the Sites is a little tricky, I usually grab and submission for the current
date. Since I grab the Dashboard/(todays datestamp)/*.xml files I do not need to a "Nightly
DashboardStart".  The proper directory structure and Update.xml will be already be in place.



-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com]
Sent: Tuesday, January 08, 2002 11:56 AM
To: Miller, James V (CRD)
Cc: dart at public.kitware.com
Subject: RE: [Dart] Dashboard rollover times.


> Should the "-" in the buildstamp name before the time only be in the 
> directory structure or actual encoded buildstamp used throughout the 
> system.  Not sure how this affects the server XSL scripts.
> 
> What will happen if a client does not update?  Will the build just
> not get reported by the server or will the server crash?
> 
> It looks like the bottom line is that buildstamps are 
> YYYYMMDDHHMM-[Nightly|Experimental|Continous]
> 
> So one change is that Experimentals are now labeled with "-Experimental"
> and nightlies have the hour and minute encoded.
> 
> In general, I do not like forcing clients to update Dart.  However,
> I don't want the code to be too complicated to support both the old
> encoding and new encoding schemes.

I just put in a small change on the branch that will allow the server to
accept Nightly and Experimental builds from clients that have not updated
Dart.  I also changed it to add the hyphen between the date and time.  It
seems to work just fine.

If you could take a look to check that the XSL scripts are okay, then it
shouldn't be a problem to merge these changes into the main tree.

-Brad