Re: [boost] Boost Testing Dashboard with Dart

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-01-11 11:02:00

Brad, this will be an enormously valuable contribution!

----- Original Message -----
From: "Brad King" <brad.king_at_[hidden]>

> I have been working with Doug Gregor to provide the Jamfile support needed
> to test Boost with Dart.  Although nightly testing with a cron-job is not
> yet in place on more than one platform, we have run many test builds by
> hand.  The current Dashboard is up at the following address:
>
> http://public.kitware.com/dashboard.php?name=boost
>
> There are links at the top of this page to the dashboards for other
> projects.  They provide good examples of builds and tests on a wide
> variety of platforms.
>
> Anyone interested can try submitting a test build to the boost dashborad.
> The necessary Jamfiles are provided in a tarball on the boost files page.
>
> http://groups.yahoo.com/group/boost/files/DartForBoost/

Are these jamfiles based on what's found in status/Jamfile? This has the
most sophisticated Jam testing code we have available, and it already tests
nearly everything.

> The tarball should be extracted into a boost CVS checkout (from the
> directory above the root).  It will over-write some of the files currently
> provided in the CVS checkout (make sure you set permissions to allow
> overwrites).  Most importantly, allyourbase.jam has been updated with Jam
> rules needed to build and run tests with Dart.  There is also a readme
> file provided in the tarball.  It contains more detailed instructions to
> submit a test build to the dashboard.  You will need to checkout the Dart
> source from our CVS repository.  The Dart client is implemented in Tcl
> (8.0 or higher).
>
> Although Dart has no problem supporting Windows builds, the Jamfiles
> provided in the tarball do not currently support it.
> The Jamfiles are
> very young, and have been written merely for showing that the testing can
> be done.  If there is interest in using this dashboard for boost, I would
> like help from Jam experts to create a more robust implementation.

I can currently test all of boost on Windows and Linux machines using at
least 6 different compilers using status/Jamfile. It seems like some
coordination would be a big help here.