[wtp-releng] WTP "Weekly" 2.0 Build "Declared"

[John Lanuti <jlanuti@xxxxxxxxxx>]

See David's notes below for the build
issues we have been having.  Nevertheless, we feel it is important
to reliably ship a weekly build for adopters to kick the tires on, so,
we have smoke tested and "declared":

http://download.eclipse.org/webtools/committers/drops/R2.0/S-2.0RC2-200706010614/

I say "declared" because notice
we will not be moving this off the committers page as not to confuse the
community in thinking we are declaring our RC2.  RC2 will be declared
as planned on June 5th and rolled into Europa RC2 on June 6th.  In
the meantime, we'll get the build infrastructure squared away which will
hopefully clear up the JUnit failures.

So, once you have PMC approval, feel
free to start releasing changes without sending a note to wtp-releng.  Based
on the amount of churn between now and Tuesday, we'll have to decide if
we want to resmoke the candidate RC2 or if just certain teams will have
to resmoke.  

Now that is a confusing declare note
for the first Friday in June.  :-)

Thanks,

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861

David M Williams/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

06/01/2007 10:09 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	" wtp-releng" <wtp-releng@xxxxxxxxxxx>
cc
Subject	[wtp-releng] Some notes on infrastructure and builds this week

Just to keep everyone informed of the same information I know, as little
as it is. 

_Some_ of the build failures and JUnit failures earlier this week have
been confirmed to be due to odd, not completely understood timing issues
on the Eclipse infrastructure. 
Not all these failures are visible, but a few times, I've seen failures
that halt the build, because something couldn't be found/checked out of
CVS. 
Then the next attempt would fail, at a different point, then again at a
different point, then finally be able to pull out enough to complete. 
One reason it was more visible on the JSF component is that both JSF and
JPT have been set to _not_ halt the build if they fail (since leaf components)
whereas WST or JST will completely halt the build, if part of it fails
(since they are not leaf components), and in the case of a complete halt,
there is nothing 
published to download page. 

What we _think_ is going on, is that some CVS check-ins are not fully "replicating"
throughout the cluster right away (maybe taking 1 to 30 minutes?, or more?)
instead of the usual "minute or less".  So, we'll keep a
closer eye on this, but not sure what there is to do, except stop checking
in so much code! :) 
I suspect mostly due to busy servers due to everyone being busy towards
release, and there was some recent DoD attacks (or something) at Eclipse
that 
might have chocked things up a bit. 


Also, I've confirmed the recent notes about "vservers" should
not effect us in WTP, and this morning's "firewall" problem in
that one JEM test is currently a mystery 
and probably transient. 

_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng