X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78E7B.8142877B@onstor-exch02.onstor.net>; Fri, 4 May 2007 11:39:10 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78E7B.8142877B"
References: <BB375AF679D4A34E9CA8DFA650E2B04E018A6972@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Automated nightly branch builds
Date: Fri, 4 May 2007 11:35:11 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D085@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Automated nightly branch builds
Thread-Index: AceOeWfWn3gmUfN+TeOBmrKkWqBIhQAACiSdAAA5x2AAAB7cGg==
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Jeff Miller" <jeff.miller@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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

Absolutely, I'll set it to post to the web server which keeps a week of =
rolling buildlog information that you can access anytime. Compilation =
breaks get sent to dl-cougar. I'll turn off install and regression until =
a little later in the process and just do the nightly compilations. Does =
that work for people?

Couple questions:

-does the make all include the linux build or is that separate?

-I'll run both opt and dbg builds, on which platforms are we ready for? =
ch bc cg??

Thanks,

-Ken


-----Original Message-----
From: Jeff Miller
Sent: Fri 5/4/2007 11:34 AM
To: Ken Renshaw; Larry Scheer
Cc: Andy Sharp
Subject: RE: Automated nightly branch builds
=20
Ken,
If it is easy to do, why not set up a Cougar build.  Can the email be =
sent only if the build breaks?  I don't think everyone wants an email if =
there is no problem.
Thanks,
Jeff
=20
-----Original Message-----
From: Ken Renshaw=20
Sent: Friday, May 04, 2007 11:25 AM
To: Jeff Miller; Larry Scheer
Cc: Andy Sharp
Subject: RE: Automated nightly branch builds

Hi Jeff.

We've got all the hooks in place to build and run basic upgrade and =
verification tests on any branch. The results will show up on the web at =
http://liszt/buildlogs and/or build auditlog emails can be sent out. The =
build script checks for compilation errors as well as warnings and flags =
as appropriate. Regarding the sync/clean steps, what I do to guarantee a =
clean slate is completely nuke the branch via rm -rf and then do a =
forced resync of the branch via p4 sync -f.

Do you want me to start the cougar branch builds then? Do you want the =
auditlog sent out daily in email, and if so to dl-cougar or just a =
subset?

Thanks,

-Ken


-----Original Message-----
From: Jeff Miller
Sent: Fri 5/4/2007 11:24 AM
To: Ken Renshaw; Larry Scheer
Subject: Automated nightly branch builds
=20
Ken and Larry,
Andy had a suggestion - do nightly builds on Cougar branch.  I'll set =
this up unless someone else wants to.
Do we do automatic builds now?  Is there a script for this that I could =
start with?

This is what I thought it should do:
P4 sync
If any changes then:
Make clean for all
Make for all
Make release for all
If any errors, email to some email list.

If we had an easy to use script then anyone who cared about a particular =
branch could set this up for that branch.

You could even set it up to run frequently, say every few minutes, if it =
could restart.  This might be nice when thing get really busy, like =
Delorean right now.

Thanks,
Jeff



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Automated nightly branch builds</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Absolutely, I'll set it to post to the web server =
which keeps a week of rolling buildlog information that you can access =
anytime. Compilation breaks get sent to dl-cougar. I'll turn off install =
and regression until a little later in the process and just do the =
nightly compilations. Does that work for people?<BR>
<BR>
Couple questions:<BR>
<BR>
-does the make all include the linux build or is that separate?<BR>
<BR>
-I'll run both opt and dbg builds, on which platforms are we ready for? =
ch bc cg??<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jeff Miller<BR>
Sent: Fri 5/4/2007 11:34 AM<BR>
To: Ken Renshaw; Larry Scheer<BR>
Cc: Andy Sharp<BR>
Subject: RE: Automated nightly branch builds<BR>
<BR>
Ken,<BR>
If it is easy to do, why not set up a Cougar build.&nbsp; Can the email =
be sent only if the build breaks?&nbsp; I don't think everyone wants an =
email if there is no problem.<BR>
Thanks,<BR>
Jeff<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Friday, May 04, 2007 11:25 AM<BR>
To: Jeff Miller; Larry Scheer<BR>
Cc: Andy Sharp<BR>
Subject: RE: Automated nightly branch builds<BR>
<BR>
Hi Jeff.<BR>
<BR>
We've got all the hooks in place to build and run basic upgrade and =
verification tests on any branch. The results will show up on the web at =
<A HREF=3D"http://liszt/buildlogs">http://liszt/buildlogs</A> and/or =
build auditlog emails can be sent out. The build script checks for =
compilation errors as well as warnings and flags as appropriate. =
Regarding the sync/clean steps, what I do to guarantee a clean slate is =
completely nuke the branch via rm -rf and then do a forced resync of the =
branch via p4 sync -f.<BR>
<BR>
Do you want me to start the cougar branch builds then? Do you want the =
auditlog sent out daily in email, and if so to dl-cougar or just a =
subset?<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jeff Miller<BR>
Sent: Fri 5/4/2007 11:24 AM<BR>
To: Ken Renshaw; Larry Scheer<BR>
Subject: Automated nightly branch builds<BR>
<BR>
Ken and Larry,<BR>
Andy had a suggestion - do nightly builds on Cougar branch.&nbsp; I'll =
set this up unless someone else wants to.<BR>
Do we do automatic builds now?&nbsp; Is there a script for this that I =
could start with?<BR>
<BR>
This is what I thought it should do:<BR>
P4 sync<BR>
If any changes then:<BR>
Make clean for all<BR>
Make for all<BR>
Make release for all<BR>
If any errors, email to some email list.<BR>
<BR>
If we had an easy to use script then anyone who cared about a particular =
branch could set this up for that branch.<BR>
<BR>
You could even set it up to run frequently, say every few minutes, if it =
could restart.&nbsp; This might be nice when thing get really busy, like =
Delorean right now.<BR>
<BR>
Thanks,<BR>
Jeff<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C78E7B.8142877B--
