|[wtp-dev] Not a reminder about tomorrow's now not-a-status meeting|
As we found during 3.20, UI tests no longer function on HIPP10(a.k.a. our existing build machine). Whatever combination of 3.18's changes caused it, the machine won't be upgraded, so we have no choice but to move to JIRO. For the sake of getting 3.20 out at all, m https://ci-staging.eclipse.org/webtools, but that has a few adoption blockers:
- Java EE project builds are failing from compilation errors because they rely on a BREE of J2SE-1.4. JIRO does not provide that one, and does not plan to add it. Combined with BVT being disabled on the old build server, Java EE builds no longer have automated BVT being performed. J2SE-1.5 would get it building, but upping to JavaSE-8 or 11 would be preferred for long term maintenance.
- Dali and Web Services have consistently failing tests. I haven't looked into all of their failures.
- Releng needs to determine how to publish builds from JIRO. The FAQ isn't as clear, to me, about that as I'd like, nor how to run those same builds locally using the same containers that JIRO is spinning up.
Jakarta EE 9 has GA'd. While I intend to complete support for it in Source Editing (JSP), being your PMC Lead hasn't conferred any special commit rights to me for the other projects and repositories, nor a surfeit of time to spend on them. Committers on the other projects will need to engage to support Jakarta EE. Honestly I took it on originally so the rest of you could spend more time on the actual deliverables, less with processes for the Foundation. Thankfully, Larry implemented support for Tomcat 10 into this release, so we can create workspace projects to test those changes against.
Back to the top