AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070917180723.3fef9025@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<ken.renshaw@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E02F3D81B@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 17 Sep 2007 18:07:47 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>
Subject: Re: nightly build script
Message-ID: <20070917180747.1256ff68@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D81B@onstor-exch02.onstor.net>
References: <20070917093143.6c69a3f1@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02F3D81B@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 17 Sep 2007 16:05:52 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> The script I use //depot/cm/build_scripts/buildver/nfxbuild.sh will
> definitely only run on my machine k2. It requires specific p4 clients
> for the build space, requires code coverage and Coverity to be
> installed, requires no_root_squash set on mightydogs Build-Trees
> volume, etc. etc.

I can comment out the stuff that doesn't matter like that stuff.  What
I don't want to happen is a whole bunch of "invisible" stuff (like
your nightly build script and other things) to suddenly break and cause
loss of coverage from process tools like nightly builds and such just
because we switched away from Redmond Hat.

> I think I can do you one better though Andy and help us both out...I
> have on order a new build server and if we're moving to Debian/Ubuntu
> I'd be more than happy to load that OS on the system instead of RHEL
> since I have to customize/genericize nfxbuild.sh to run on it anyway.
> My plan is to make the core portions of the build script portable and
> keep the official posting/regression/anaylsis steps as separate
> options, so you'd be able to use the script once it's ready.

I don't want to use the script ~:^)  But I don't want to hear that it
isn't running because we switched to Ubuntu either.  That would mean
I failed to think ahead.  I'm just trying to sync up as much as I can
think of for the upcoming change.

> I imagine Ubuntu supports the newest processors, e.g. the new quad
> core Intels?? The new build server is running dual quad cores.

The kernel != the distro.  But I've not seen any quad cores in house.
Which build server is that?  Besides,  Intel quad cores su@k.  All that
FSB nonsense and weakling power/mips ratio.  But seriously, it won't
have any effect.

> When the machine arrives I'll get the OS loaded and inquire as to
> your recommended toolset and we can go from there. 

There is a lot of work that has to be done before the make works on
Debian/Ubuntu, so don't need to be rushin' into anything.

> Thanks,
> 
> -Ken
> 
> 
> 
> 
> -----Original Message-----
> From: Andy Sharp
> Sent: Mon 9/17/2007 9:31 AM
> To: Ken Renshaw
> Subject: nightly build script
>  
> Hi Ken,
> 
> Can you point me to your nightly build script?  I need to see if it
> will run on ripper.  As we are moving to an Ubuntu based workstation,
> I've been tasked with making sure that our build system works under
> Debian/Ubuntu.  Besides getting the actual build to work, I wanted to
> get my hands on a few ancillary scripts that people have that do
> builds to make sure that those will work as well.
> 
> Thanks,
> 
> a
> 
