M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
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
2 weeks, 4 days
Advice for building jbosstools-* projects using the new photon-based target platform
by Nick Boldt
Until all the projects are updated to build cleanly with the new
Photon-based dependencies (like Red Deer 2.1 instead of 2.0 and Eclipse 4.8
instead of 4.7.3a), and have built in Jenkins, you'll have to build the
whole set of projects locally in order to build a downstream one like
jbosstools-central.
As you can see from the root pom [1], Central depends on several upstream
projects:
base, server, javaee, portlet (?), jst, hibernate, vpe.
[1]
https://github.com/jbosstools/jbosstools-central/blob/master/pom.xml#L27-L62
Once you've built the upstream projects locally (using `mvn clean install
-DskipTests if you're in a hurry), you can then pass those urls to the
downstream builds with
-Djbosstools-server-site=file:///path/to/jbosstools-server/site/target/repository/
You could also build using the older parent pom, version
4.7.3.Final-SNAPSHOT, but then pass in these variables to ensure you're
using the correct TP and will be correctly nagged about version bumps where
needed:
-DTARGET_PLATFORM_VERSION_MIN=4.71.1.Final
-DTARGET_PLATFORM_VERSION_MAX=4.73.1.Final
-DTARGET_PLATFORM_CENTRAL_MAX=4.73.0.Final-SNAPSHOT
-DBUILD_ALIAS=AM1
Hope that helps!
Meanwhile, base, forge, fuse extras, and the openshift restclient are
*green*. Let's get the rest fixed ASAP!
[2]
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
7 years, 10 months
ACTION REQUIRED: JBoss Tools + Developer Studio triage time
by nboldt@redhat.com
As the current sprint 'devex #147 April 2018' draws to a close, it is time
to review your unresolved issues!
Some may be done (or will be done soon), but the JIRA(s) need resolution.
Others may need to be pushed to the next milestone (4.6.0.AM1 + 12.0.0.AM1),
to a future .x release, or LATER.
All unresolved issues for 4.5.3.Final + 11.3.0.GA:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.5.3.Final + 11.3.0.GA:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
Once created, you can also begin scheduling your work for the upcoming
sprint, 'devex #148 April 2018'.
Triage tips:
* blocker/critical issues: make these your priority work for the next sprint:
move to next version & assign to the next sprint
* other issues that WILL be done in the next sprint:
move to next version & assign to the forthcoming sprint, but lower down
* non-blocker & non-critical issues not for the next sprint:
move to .x (or LATER)
7 years, 10 months