I like the idea of GlassFish doing its own TCK testing when the TCK is finalised and the Jakarta EE version we are testing is released. I think if the TCK is a moving target and GlassFish is a moving
target e.g. during platform development e.g. 9.1 it becomes more problematic.
I found the way of working for the 9 release whereby the TCK was doing GlassFish testing good as GlassFish project lead I could worry about fixing the GlassFish bugs and not have to worry about which
release of the TCK to test and where the TCK was in its development cycle. However I understand that may push the burden to the TCK team
😊
Anyway someone with knowledge of getting the TCK up and running on GlassFish will need to step up to create the Jenkins jobs on the GlassFish project as I have no idea how to do it.
Steve
From: arjan tijms <arjan.tijms@xxxxxxxxx>
Sent: 10 February 2021 18:37
To: Scott Marlow <smarlow@xxxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>; Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx>; Gurunandan <gurunandan.rao@xxxxxxxxxx>
Subject: Re: [glassfish-dev] Merge of 6.1 branch to master
Are we planning to run the TCK on the GlassFish Jenkins still?
That's a very good question. I like the idea of kicking off a basic TCK test from the GF project. On the other hand, the GF CI, due to it being a collection of many projects, not just the AS, is already a little
complicated (perhaps that's an understatement even).
Also, the GF CI probably has less resources provisioned for it right now?
Steve
Hi,
Thanks! The status is as follows:
The PR includes the work done earlier by Fujitsu and my work where I updated the command security plugin to support JDK 11 and replaced all usages of sun.* classes that either disappeared entirely, or were made invisible.
I tried to replace as much as possible with public alternatives. Eg “jarsigner” moved to a public API, and “FilePolicy” could be obtained via a public API. For some other code, like PropertyExpander I had to replace it with new code of myself.
The code compiles, and the unit tests pass. GF starts up enough to generate the domains during the build, but beyond that no tests have been done.
* Start GF manually and inspect logs
* Start admin console and test if it all works
* Run TCK and fix failures (likely fix in both TCK and GF)
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
|
