Over the weekend, we got clean builds for *MOST* of the components.
However, I'm tracking test failures for the following 6 components. Some
may have broken BEFORE the update to the target platform but we didn't
see it because the jobs were turned off in order to crank out M5 builds
for QE last week.
I also have one compilation failure, which I can reproduce locally after
updating to latest trunk sources:
Unless you're working on fixes/testing/doc for M5, or are currently AFK
on PTO, can you please take a look at these issues and get them cleaned
up before the holiday shutdown? Much as I love seeing red, yellow, and
green coloured balls this time of year, I'd love to see ONLY blue
decorating the Jenkins tree. :)
On 12/16/2011 10:30 PM, Nick Boldt wrote:
Components in trunk are now spinning against the updated TPs.
Note that after the Jenkins server restart this morning at 7am GMT, some
of my ant scripts were no longer working. I've fixed the biggest issue
which was causing numerous builds to fail during their publishing step
(Ant was not respecting the classpath declaration of an XSLT operation,
so couldn't use Saxon for the transformation), but I'm seeing more test
failures than before which suggests there may be other issues to come.
One of the perks of the restart, however, was that we now have
additional columns in the job view for upstream and downstream
Anyway, here's to clean spins over the weekend and good trunk bits for
testing on Monday.
Have a good weekend everyone -- and if you're AFK between now and New
Years, happy holidays too!
(I'll be offline Dec 26 - Jan 6 but will be around to check mail from
time to time.)
On 12/15/2011 07:19 PM, Nick Boldt wrote:
> New trunk target platforms are under way:
> With any luck they'll both complete successfully in an hour or so, then
> kick off the downstream component jobs which will also run successfully.
> That said, expect some breakage as the trickledown happens. If you see
> your component's job has died, see if its upstream jobs were successful
> and if so, respin yours. If upstream died, feel free to respin the
> upstream jobs.
> As always, the trunk jobs can be seen here:
> On 12/15/2011 01:54 PM, Nick Boldt wrote:
>> With M5a out the door this morning to QE, and testing well underway,
>> I've turned OFF all the _stable_branch jobs toward M5, and will be
>> turning the trunk jobs back ON soon - please continue to build locally
>> before committing changes in trunk to verify that Tycho's happy w/ all
>> your new hard work.
>> I'm going switch trunk over to build against the new SR1-M bits so we
>> can see if anything breaks. Reminder, we only have until *January 13* to
>> report problems to upstream projects in the Indigo release train. After
>> that they're into code freeze for their RC builds and getting anything
>> changed will be harder than getting Max to say something nice about
>> EMF. :D
>> I'll send a followup when trunk starts spinning against the new TP. M5
>> will still be set to run against the old SR1 TP so as to minimize the
>> impact on QE - this of course means that the new TPs will have a
>> different URL than the previous, so for those in Europe, you'll have to
>> deal w/ some delay as everything mirrors from Boston to Brno. Can't be
>> helped, I'm afraid.
>> On 12/13/2011 03:28 PM, Nick Boldt wrote:
>>> I have a new requirements mirror in place for anyone to play with.
>>> The SR1-M site is completely new, whereas the extras SR1a site is the
>>> same site as before, except it now contains a patched version of Spring
>>> IDE 2.7.2 which won't break your Welcome screen (JBDS-1966).
>>> Next, I'll be creating new target platforms based on this new site
>>> On 11/30/2011 02:53 PM, Nick Boldt wrote:
>>>> With Xmas just around the corner, holiday shutdowns coming, and Indigo
>>>> SR2 being released February 24 2012 , the runway to get fixes into
>>>> Eclipse, WTP, DTP, BIRT, RSE, Mylyn, etc. is increasingly short.
>>>>  http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan#SR2
>>>> Based on their RC schedule, and how hard it is to get fixes done
>>>> the RC cycle, I would say the hard deadline for ANYTHING to be
>>>> fixed in
upstream bits is *January 13*, which means you need to get
>>>> bugs filed, if necessary, at least a week or two before that.
>>>> To that end, I'd like to have people start testing their builds
>>>> w/ the latest Eclipse Indigo  bits.
>>>>  http://download.eclipse.org/releases/maintenance/
>>>> In the next few days, I'll put together a new composite requirements
>>>> site  and TP  using these updated versions so it'll be easier
>>>> test w/o being restricted by Eclipse.org
>>>>  http://download.jboss.org/jbosstools/updates/indigo/SR1/
>>>> As a reminder, should you feel you need something added to (or updated
>>>> in) the TP or reqs composite sites to facilitate building, running,
>>>> installing, or testing any part of JBoss Tools (or Developer Studio),
>>>> PLEASE ASK FIRST via direct email, mailing list, or JIRA.
>>>> We recently found a new requirement on a JDT patch feature, which I
>>>> erroneously added to the TP assuming that it should have been there. I
>>>> tend to assume any new requirements are added intentionally, but we
>>>> to ensure we're properly communicating so that accidental
>>>> aren't added and cause build issues.
>>>> For reference, here are the latest updates to the TP over the last
>>>> month, based on svn log data:
>>>> 11/28: remove org.eclipse.objectteams.otdt.core.patch
>>>> 11/25: add org.eclipse.objectteams.otdt.core.patch
>>>> 11/23: BPEL updated from 0.5 to 0.8
>>>> 11/07: Mylyn/JIRA added (JBIDE-9351, JBIDE-10094)
>>>> 10/27: Mylyn
>>>> 10/26: Mylyn eGit connector (JBDS-1904)
>>>> 10/25: apache.commons.io 2.0.1 added
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio