X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7CE33.FEF591BB@onstor-exch02.onstor.net>; Tue, 24 Jul 2007 12:48:31 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CE33.FEF591BB"
References: <20070724134505.2510fa44@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: nightly builds?
Date: Tue, 24 Jul 2007 12:46:32 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D51D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: nightly builds?
Thread-Index: AcfOM4RCmQAJyeZoSj2TxZGcyEbaTQAADOuM
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CE33.FEF591BB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sure Andy. I'm working on tying Covery into nightly runs as well per =
mgmt request and by tomorrow night the whole shebang should be up and =
building, linux targets inclusive. I assume you want all build emails, =
not just the build failures though, correct Andy?=20
=20
Thanks,
=20
-Ken

________________________________

From: Andy Sharp
Sent: Tue 7/24/2007 1:45 PM
To: Ken Renshaw
Cc: Larry Scheer; Tim Gardner
Subject: nightly builds?



I checked with the cougar team: no one is getting nightly build
emails.  Please configure the nightly builds to send an email upon
build failure to dl-cougar.  That goes for all the builds done in the
cougar branch regardless of PROD or VARIETY or whatever silly variable
names we are using.

Thank you,

a



------_=_NextPart_001_01C7CE33.FEF591BB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>nightly builds?</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText36708 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Sure Andy. =
I'm working on tying Covery into nightly runs as well per mgmt request =
and by tomorrow night the whole shebang should be up and building, linux =
targets inclusive. I assume you want all build emails, not just&nbsp;the =
build failures though, correct&nbsp;Andy? </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Ken</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Andy Sharp<BR><B>Sent:</B> Tue =
7/24/2007 1:45 PM<BR><B>To:</B> Ken Renshaw<BR><B>Cc:</B> Larry Scheer; =
Tim Gardner<BR><B>Subject:</B> nightly builds?<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I checked with the cougar team: no one is getting =
nightly build<BR>emails.&nbsp; Please configure the nightly builds to =
send an email upon<BR>build failure to dl-cougar.&nbsp; That goes for =
all the builds done in the<BR>cougar branch regardless of PROD or =
VARIETY or whatever silly variable<BR>names we are using.<BR><BR>Thank =
you,<BR><BR>a<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7CE33.FEF591BB--
