[Dart] Combined projects on one dashboard

Jim Miller millerjv at gmail.com
Sat May 13 08:36:19 EDT 2006


John,

How would you like the information from the N projects to appear on the
dashboard?

Do you want it show only two clients with reach client showing the
results of all the projects (vtkCSCS, vtk, Paraview, etc.)?

One way to do this now is to create a dummy parent project with a
CMakeLists.txt file under which you place your checkouts of
vtkCSCS, vtk, Paraview, etc.  This might take a bit a CMakery
to get the parent project setup correctly to build all the subprojects.
But then all the results from the subprojects would be summarized
together on one line on the dashboard.

As CTest and Dart evolve, we should be able to specify a subproject
name for a build.  In Dart, all tests etc. are store hierarchically as
".Test.Code.Common.itkIteratorTest" or some such name (or as
".Build.#####", etc.)  In the future, CTest will probably produce
Dart2 XML files (I think Dan still needs to produce the XML schema
for this, but the Dart2 format is used for archival today.) and then
the results could come in as
".Test.<SubProject>.Code.Common.itkIteratorTest"
or etc.  This will be a more natural way to do it.

Another alternative in the future would be to make use of multiple "tracks".
The tracks in Dart 2 can be named anything.  To support Dart Classic
submissions, we default the tracks to be named "Nightly", "Continuous", etc.
There is no reason you couldn't have tracks named "vtkCSCS", "vtk",
"Paraview",
etc. This just requires we formulate a mechanism to have CTest indicate a
project
specific track name.  Again, this can be done when we start using the Dart2
XML
format in CTest. In this scenario, you can use the same client names for
each
subproject but the each subproject would appear as a distinct section of the

Dashboard.

So how would you like to have the data presented on the dashboard? All
subprojects
merged together on one line of the dashboard?  Or each subproject having its
own
track?

These are not mutually exclusive.  In fact, if the former is used, we could
provide
an alternative dashboard page that made it appear as the latter.

As for the timezones, each track has its own "cycle" with the cycle of the
"Default"
track governing the default navigation.  The start times specified in
Project.xml are in
the timezone of the server.  With multiple projects going to the same
dashboard, I do
not think it is so much a timezone issue as much as each  project running on
its own
cycle put submitting to a dashboard governed by a single cycle.

I think the easiest thing to do have all these projects use the same start
time.  It
doesn't matter what time you actually perform the build/tests, the updates
will always
be locked to the nightly start time.  So if you can sync the
NightlyStartTimes
for each project and the dashboard, then you should be all set.

If we wind up taking the approach above where each project appears on a
separate
track on the dashboard, then each of these tracks can be configured with
different
NightlyStartTimes.  Thus, all projects could run on a 24 hour clock, but
each track
may be shifted in time.  Let's say your code is the default track and vtk's
track
starts 3 hours earlier.  Then when you bring up your dashboard, it will show
you
your project's data and vtk's data during the period that the two cycles
overlap.
The two track timelines would look something like...

-----p--------------p--------------p--------------p
v--------------v--------------v--------------v--------------v




On 5/12/06, John Biddiscombe <biddisco at cscs.ch> wrote:
>
> I've just upgraded dart to the trunk after having the current dashboard
> running continuously for over 6 months and I can't remember when I last
> updated dart before that...
>
> Upgrading was simple. I wiped everything (who cares!) and rebuilt.
> Running again in just 5 minutes. Things look different. hmmm, interesting.
>
> Question 1 :
> I'd like to have N projects vtkCSCS, vtk, Paraview, ProjectX, projectY,
> etc etc all displayed on the same dashboard. With probably 2 machines
> per build.
> Previously, I've just modified the Site name to be "ProjectName-Machine
> Name" and lived with it looking a bit odd.
> I want to avoid having ten dashboards with just 2 entries per day and
> like to have all projects built and submitted to one.
>
> Is there a nice neat way of doing it now, or shall I just live with the
> existing hack?
>
> Question 2:
> We do a nightly build of our stuff using Central European Time, but a
> nightly checkout of vtk/paraview on Eastern US time. I know this is a
> FAQ, but is there a WIKI entry for setting up time zones. I messed mine
> up before and we always did a nightly update at about midnight here and
> got vtk submitted to our "Yesterday" dashboard, with our stuff on
> "today" - I'd like to get this right for once.
>
>
> thanks
>
> JB
>
>
>
> --
> John Biddiscombe,                            email:biddisco @ cscs.ch
> http://www.cscs.ch/about/BJohn.php
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
> Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82
>
> _______________________________________________
> Dart mailing list
> Dart at public.kitware.com
> http://public.kitware.com/mailman/listinfo/dart
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/dart/attachments/20060513/61534f12/attachment.htm


More information about the Dart mailing list