RE: [cross-project-issues-dev] endgame for the Europa Winter Maintenance

["Mik Kersten" <beatmik@xxxxxxx>]

Thanks for scheduling those builds Markus, that's helpful.

It looks like the suggested 2pm time was a no go because the build would
have needed to be manually invoked. 

Unless a new build is spun, on Mylyn we'll wait for the regularly scheduled
5pm EST build, test the Europa packages from that, and then test the 8:40pm
EST EPP build that Markus has scheduled.

Mik

> -----Original Message-----
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-
> project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Markus Knauer
> Sent: Tuesday, February 26, 2008 1:37 PM
> To: Cross project issues
> Subject: Re: [cross-project-issues-dev] endgame for the Europa Winter
> Maintenance
> 
> Here an update:
> 
> There was a Europa update site build started started February 26, 2008
> 11:20:18 AM EST http://dash.eclipse.org/~bfreeman/europa/
> 
> Based on this build is the EPP Europa build '20080226-2035'
> http://www.eclipse.org/epp/download.php
> 
> I've added two additional EPP builds in my crontab:
> * 8.40pm EST
> * 1.40am EST
> 
> That said, it should be possible to run an additional Europa update
> site build
> at 6pm (should be enough time to be used by the 8.40pm EPP build), and
> another one at 10pm.
> 
> That way, it could be possible to see additional results today. And if
> this is
> not the case, we should see them tomorrow. :-)
> 
> I hope this helps.
> 
> Markus
> 
> 
> 
> On Tuesday 26 February 2008, Mik Kersten wrote:
> > The current build is failing, probably due to new BIRT and TPTP
> features
> > being updated while the build is running.  At least that's what
> happened
> > with Mylyn last week when we got the "No Matching Features" with
> Mylyn.  On
> > Mylyn we haven't updated our features to yesterday's final build in
> trying
> > to avoid the break, but since are broken already are updating our
> features
> > right now.
> >
> > 	http://dash.eclipse.org/~bfreeman/europa/
> >
> > Could we make an end-game plan something along these lines to
> minimize
> > build breakage? This just boils down to batching our re-spin requests
> so
> > that those like Mylyn that need to do cross-project testing of
> packagings
> > can know when to do so.  Proposed times are in build server time
> (EST).
> >
> > Today, 2pm EST: first freeze (manually triggered build)
> > * Everyone has submitted their bits and won't do so again until the
> build
> > goes green.
> > * Markus: after the build has run, and hopefully gone green, I assume
> that
> > some number of hours later we can expect the EPP packaging of it at
> the
> > usual URL?  How long does it usually take?
> > http://www.eclipse.org/epp/download.php
> >
> > Today, 8pm EST: second freeze (usual time the build runs)
> > * Same as above, but given build times testing of the result waits
> until
> > tomorrow.
> >
> > Tomorrow: something like the above two freezes for anyone who needs
> last
> > minute changes.
> >
> > Mik
> >
> > --
> > Mik Kersten
> > President & CTO, http://tasktop.com
> > Project Lead, http://eclipse.org/mylyn
> >
> >
> >
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> 
> 
> --
> Markus Knauer
> INNOOPRACT Informationssysteme GmbH
> ###   phone: +49 721 664 733 0  (GMT +1)
> ###     fax: +49 721 664 733 29
> ###     web: www.innoopract.com
> 
> ========================= Legal Disclaimer
> =================================
> According to Section 80 of the German Corporation Act
> Innoopract Informationssysteme GmbH must indicate the following
> information:
> Address: Stephanienstrasse 20, 76133 Karlsruhe Germany
> General Manager: Jochen Krause, Eric von der Heyden
> Registered Office: Karlsruhe, Commercial Register Karlsruhe HRB 7883
> =======================================================================
> =====
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev