From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fei, Fei" Subject: Re: Keep last 3 nightly builds (tarballs) around ifpossible? Date: Tue, 05 Apr 2005 14:26:03 +0800 Message-ID: <42522F7B.6090604@intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1684154160==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1684154160== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Talking about the nightly builds, is there automated
testing infrastruture thing around there after each nightly
build?

Fei

Ian Pratt wrote:

>>Was wondering if it would be possible to keep around more

>>than one day's worth of unstable (and possibly testing)

>>tarballs? Perhaps 2, or even 3?

> Are you talking src, binaries or both?

I was talking src, but I expect other people have different

needs(?). Both would be very handy, of course.

> I've updated the script to rename the previous night's builds to

> xen-2.0-install.1.tgz the night before to .2 etc. It keeps the last

> three builds.

Excellent! Many thanks..

> I guess I should probably switch to using dates as snapshot identifiers,

> but that requires more thought.

The above works (consistent with usual logging backups

etc (syslog et al).

thanks,

Nivedita

--===============1684154160== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1684154160==--