Norman,
My overall plan for the development systems which I am working on now is:
1. The whole of the Starlink software development tree should be built
by the nightly build. The development computers will then be saturn and
rlsul0. This will provide constant update info to developers, me and
users, plus reduce allot of the grunt-work I have to do. Most of the
basic software submission checks can be automated, allot more time can then
be given to testing.
There is nothing special about the OS/environment setup of any of the
development/control computers; you only need the compiler/OS versions. The
nightly build does nothing special, other than choose arbitrary locations to
build and install the software (no /star or /stardev).
2. Control systems will be backed up and the frozen. There's not enough
money to maintain the extra computers.
3. I have to write lots of documentation about building our software
for the development page. It does say on the development page now
that the nightly build is done on RedHat 9.0 and gives the relevant JDK,
JRE and JAI version numbers. The only thing I need to add is the GCC/G77
versions on the RedHat 9.0 system. Solaris will be added soon, with
appropriate compiler/OS versions indicated.
4. Not having all the software under CVS is an annoyance, it would make life
so much easier.
-----Original Message-----
From: Norman Gray [mailto:[log in to unmask]]
Sent: 27 November 2003 11:10
To: [log in to unmask]
Subject: Re: BUILD FAILED
Steve,
On Thursday, November 27, 2003, at 10:44 AM, Rankin, SE (Stephen) wrote:
> I sent the message below yesterday.
> From: Rankin, SE (Stephen) [mailto:[log in to unmask]]
> Sent: 26 November 2003 13:14
> To: [log in to unmask]
> Subject: Re: BUILD FAILED
>
> Peter,
>
> OK, the nightly build is now using JDK 1.4.2_02 and JAI 1.1.2.
True, I dimly remember that now, though I don't have the message any
more. My fault.
It would still be useful if there were some build-system notes in the
buildlog part of the CVS tree. Would that sort of thing be easy to do?
Also, the HardwareDetails page of the wiki lists rlsaxps, rlsul2 and
rlspc1 as the `CONTROL' machines: is it feasible to ensure that these
machines have a duplicate, or compatible, environment to that used to
do the nightly builds? If the build environment notes were generated,
then regenerating and comparing them could be a useful part of the
nightly build.
I've been looking a bit at
<http://acme.bradapp.net/repro/SoftwareReconstruction.html> as part of
the autoconfing stuff. That comes from the same place as the branching
patterns stuff I've mentioned before. Though it's much more of a draft
than the branching stuff, it has a fair amount of detail about the
patterns of build reproduction, and includes the `nightly build'
pattern. Since you're designing the overall project CM system, this
and its references might be useful.
See you,
Norman
--
----------------------------------------------------------------------
Norman Gray http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow [log in to unmask]
|