Re: [glassfish-dev] EE 12 Platform TCK + GlassFish TCK testing CI + http

[David Matejcek <david.matejcek@xxxxxxxxxxx>]

Hi, 

Sorry I forgot the meeting again!

We have a plan to do so soon, but the priority is to finish release of 7.1.0 and 8.0.0. Maybe we can do it bit earlier, now we are still resolving partially released artifacts (Concurro, Epicyro) which were lost in staging and never made it to Central. So probably after we win this fight (few days), we can fork 9.0. 

Then I am also in progress of using TCK 11 directly in GlassFish - similar as OpenLiberty I have found several issues and contributed fixes for them. I would like to avoid any chaos of changes/challenges in some branches and missing in another. 

I know that there is a huge pressure for TCK12, we are doing our best.

-- 
David Matejcek | OmniFish
david.matejcek@xxxxxxxxxxx

On 14/10/2025 19:21, Scott Marlow wrote:

Resending as I don't see the below message on https://www.eclipse.org/lists/glassfish-dev/maillist.html

On Wed, Oct 8, 2025 at 10:57 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hello,

https://github.com/jakartaee/platform-tck/issues/2476 is for tracking the GlassFish 9 + Jakarta EE 12 TCK testing assignments from the point of view of the Platform TCK effort for EE 11.  We are hoping that the EE 12 development/release will not involve major changes to the TCK tests but there will be changes as needed.  As I understand the GlassFish project there are forks of GlassFish that some developers contribute to and some others contribute to the main GlassFish source.  Regardless, I'd like to ask whom from the GlassFish community can sign up to help with setting up the GlassFish CI jobs for EE 12?  Perhaps update https://github.com/jakartaee/platform-tck/issues/2476 with comments that you are volunteering.  

I wonder if we can create a GlassFish CI folder for EE 12+ under ci.eclipse.org/jakartaee-tck/glassfish?  

Would it also make sense to also have a https://github.com/jakartaee/platform-tck/tree/glassfish9 branch for GlassFish to test the EE 12 TCKs?  I think we need to separate TCK commits from GlassFish TCK runner commits as the TCK changes make it harder to read the GlassFish TCK runner commit history.

If you want to volunteer to be one of the Platform TCK CI champions to setup TCK runner jobs for EE 12, please comment on https://github.com/jakartaee/platform-tck/issues/2476 as well that you can do that.  

Thanks + regards,

Scott