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
ACTION REQUIRED: JBoss Tools + Developer Studio triage time
by jmaury@redhat.com
As the current sprint 'devex #185 June 2020' 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.16.0.Final + 12.16.0.GA),
to a future .x release, or LATER.
All unresolved issues for 4.16.0.AM1 + 12.16.0.AM1:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.16.0.AM1 + 12.16.0.AM1:
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 #186 July 2020'.
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)
5 years, 8 months