Re: Keep last 3 nightly builds (tarballs) around ifpossible?

Re: Keep last 3 nightly builds (tarballs) around ifpossible?

[Fei, Fei]

[-- Attachment #1: Type: text/html, Size: 3048 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: Keep last 3 nightly builds (tarballs) around ifpossible?

[Ian Pratt]

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

The LTP guys have created one. It would be great if more people could
run it and help extend it.

http://article.gmane.org/gmane.comp.emulators.xen.devel/7013/match=xente
st


Ian 

RE: Keep last 3 nightly builds (tarballs) around ifpossible?

[Ian Pratt]

> 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'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.

I guess I should probably switch to using dates as snapshot identifiers,
but that requires more thought.

Ian

Re: Keep last 3 nightly builds (tarballs) around ifpossible?

[Nivedita Singhvi]

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

RE: Keep last 3 nightly builds (tarballs) around ifpossible?

[Paul Larson]

[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]

On Tue, 2005-04-05 at 01:18 +0100, 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'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.
> 
> I guess I should probably switch to using dates as snapshot identifiers,
> but that requires more thought.
Dates for the archived copies would be great, but if possible, it would
be really nice if we could keep a consistent name for the latest
snapshot.  That makes automation quite a bit simpler.

-- 
Thanks,
Paul Larson
pl@us.ibm.com
IBM Linux Technology Center

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel