[Springframework-developer] testing / nightly builds

[Darren D. <da...@da...>]

After complaining to SF about the lack of JDK's in their compile farm, I=20
found six of them.  Unfortunately for me, I'd checked the only 4 machines=20
that *didn't* have one before writing to them.  Me and my mouth.

Anyway, I now intend to attempt scheduled builds on five of the six machine=
s=20
(2 are identical in terms of OS and JDK) and of course run the test suite. =
=20
Once I have this working well, I'll attempt to run the autobuilds apps on=20
each supported servlet container (again on all five machines).  The=20
advantage of the compile farm is in the range of platforms available.

I'd like to get each machine to send an email to the dev list, but only on =
a=20
build failure unless anyone sees value in an additional five daily emails=20
showing successful builds.  Another option to investigate is FTP'ing the=20
report summaries somewhere - like the project web server to which we could=
=20
presumably link from springframework.org...?

Note though, that the CVS access on the CF machines is via the anonymous=20
pserver which can be up to 5 hours behind the SSH servers that we commit=20
changes to.

Here's some detail on the machines that I'll be running this on:

machine            JDK               OS
=2D---------------------------------------------------------------------
x86-solaris1       Sun 1.4.1_06      Solaris 9
amd64-linux1       Sun 1.3.1         SUSE 8 (linux 2.4)=20
ppc-osx1           Sun 1.3.1         Mac OSX 10.1
ppc-osx2           Sun 1.4.1_01      Mac OSX 10.2
sparc-solaris1     Sun 1.4.0_03      Solaris 9



I note that there are a couple of outstanding requests at SF to add a JDK=20
1.5 to one of the machines too, so when that becomes available I'll use it=
=20
too.  Hopefully this will give us some additional confidence in the build=20
process, test suite and JDK/container compatibility.

Regards,

=2D-=20
Darren Davison
Public Key: #DD356B0D