X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7CE35.072D929D@onstor-exch02.onstor.net>; Tue, 24 Jul 2007 12:55:55 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CE35.072D929D"
References: <20070724134505.2510fa44@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D51D@onstor-exch02.onstor.net> <20070724135106.5f4efba5@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: nightly builds?
Date: Tue, 24 Jul 2007 12:52:29 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D51E@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: nightly builds?
Thread-Index: AcfONFtJFM9vVPkCTB6X6XvDt6IsnAAADFi2
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_01C7CE35.072D929D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

For bsd targets, yes; for linux targets no. it was 7/11 when Jeff passed =
on that the linux targets ( except for release I'm still told ) was =
working and hence ready. Then the global request for merging zonda and =
cougar took over, and two weeks later here we are. I was kind of hoping =
we wouldn't be in the cougar branch for very long, since changing all =
the names for only a week's run wasn't terribly palatable, neither dev =
having to create clients for only a short time. Chris as an example.=20
=20
Short answer: I'm working on it and once people stop pulling the rug out =
at every turn it'lll help immensely.

________________________________

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



Sure, but I thought all this was up and working a long time ago.

On Tue, 24 Jul 2007 13:46:32 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> 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? Thanks,
> -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_01C7CE35.072D929D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: 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=3DidOWAReplyText12004 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>For bsd =
targets, yes; for linux targets no. it was 7/11 when Jeff passed on that =
the linux targets ( except for release I'm still told ) was working and =
hence ready. Then the global request for merging zonda and cougar took =
over, and two weeks later here we are. I was kind of hoping we wouldn't =
be in the cougar branch for very long, since changing all the names for =
only a week's run wasn't terribly palatable, neither dev having to =
create clients for only a short time. Chris as an example. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Short answer: I'm working on =
it and once people stop pulling the rug out at every turn it'lll help =
immensely.</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:51 PM<BR><B>To:</B> Ken Renshaw<BR><B>Cc:</B> Larry Scheer; =
Tim Gardner<BR><B>Subject:</B> Re: nightly builds?<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Sure, but I thought all this was up and working a long =
time ago.<BR><BR>On Tue, 24 Jul 2007 13:46:32 -0700 "Ken =
Renshaw"<BR>&lt;ken.renshaw@onstor.com&gt; wrote:<BR><BR>&gt; Sure Andy. =
I'm working on tying Covery into nightly runs as well per<BR>&gt; mgmt =
request and by tomorrow night the whole shebang should be up and<BR>&gt; =
building, linux targets inclusive. I assume you want all build<BR>&gt; =
emails, not just the build failures though, correct Andy? =
Thanks,<BR>&gt; -Ken<BR>&gt;<BR>&gt; =
________________________________<BR>&gt;<BR>&gt; From: Andy =
Sharp<BR>&gt; Sent: Tue 7/24/2007 1:45 PM<BR>&gt; To: Ken =
Renshaw<BR>&gt; Cc: Larry Scheer; Tim Gardner<BR>&gt; Subject: nightly =
builds?<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; I checked with the cougar team: =
no one is getting nightly build<BR>&gt; emails.&nbsp; Please configure =
the nightly builds to send an email upon<BR>&gt; build failure to =
dl-cougar.&nbsp; That goes for all the builds done in the<BR>&gt; cougar =
branch regardless of PROD or VARIETY or whatever silly variable<BR>&gt; =
names we are using.<BR>&gt;<BR>&gt; Thank you,<BR>&gt;<BR>&gt; =
a<BR>&gt;<BR>&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7CE35.072D929D--
