Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
I'm trying to build org.jboss.tools.vpe.browsersim.eclipse.test locally
to reproduce its failure on Hudson. But I got an error*
*/[ERROR] Cannot resolve project dependencies://
//[ERROR] Software being installed:
org.jboss.tools.vpe.browsersim.eclipse.test////3.5.0.qualifier//
//[ERROR] Missing requirement:
org.jboss.tools.vpe.browsersim.eclipse.test 3.5.0.qualifier requires
'bundle org.jboss.tools.tests 3.5.0' but it could not be found/
During local built all dependencies must be resolved by tycho and
downloaded from our servers, am I right? How this problem can be fixed?
Done for cordova tools...
I replied to Nick in the first time
---------- Forwarded message ----------
From: Gorkem Ercan <gorkem.ercan(a)gmail.com>
Date: Thu, Jun 27, 2013 at 10:10 PM
Subject: Re: [jbosstools-dev] ACTIONS REQUIRED :: Branching today for CR1
and future 4.1.x releases
To: Nick Boldt <nboldt(a)redhat.com>
All clear for cordova tools
--
Gorkem
On Thu, Jun 27, 2013 at 11:49 AM, Nick Boldt <nboldt(a)redhat.com> wrote:
> Today is CODE AND FEATURE FREEZE for the upcoming JBT 4.1.0 / JBDS 7.0.0
> releases.
>
> Project leads are required to (at some point today) do the following 5
> steps:
>
> a) switch their project's root pom to point at the JBT parent pom
> version 4.1.0.CR1 (not Beta2 or Beta3).
>
> b) rebuild locally to verify everything still works w/ the updated
> parent pom + target platform
>
> c) read the build log to verify that the TP used is Beta1, and pulls
> Kepler R bits (rather than an Alpha TP with pre-release Kepler bits)
>
> d) create a branch in their project called jbosstools-4.1.x, which will
> be used to build CR1, CRx, GA, and future maintenance.
>
> e) reply to this thread confirming that you're branched and ready for
> CR1 builds to begin this weekend.
>
> ---
>
> Since we are frozen for CR1 today, please keep your changes in the 4.1.x
> branch to a MINIMUM. CRITICAL / BLOCKER issues only, vetted by at least
> 1 other person via JIRA + PR review. Other issues still open against
> your component should be triaged out to the next release (4.1.1 or
> 4.2.x, as fitting).
>
> ---
>
> After branching, master branch will be open for 4.2.x development
> against Eclipse 4.4 (Luna), but we will not have a Luna-based target
> platform for some time. You can also work on 4.1.x / 7.0.x bugfixes
> there, but please track which ones will need to be backported to 4.1.x /
> 7.0.x maintenance releases.
>
> After we release 4.1.0.Final / 7.0.0.GA, the 4.1.x branch will reopen
> for MAINTENANCE FIXES ONLY, and any approved bugfixes done in master
> which need to be backported to the .x branch can be done AT THAT TIME.
>
> ---
>
> Any questions or concerns with this plan, please don't hesitate to ping
> me, Mickael, Max, or Denis, or reply to this thread.
>
> Cheers,
>
> Nick
>
>
> On 06/27/2013 10:57 AM, Max Rydahl Andersen wrote:
> > The branch to use for cr1 is: jbosstools-4.1.x
> >
> > Thats where we will cut cr and final releases from.
> >
> > /max (sent from my phone)
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
