Mark,

On 7/22/24 12:53, Mark Thomas wrote:
All,

Today I have configured the tomcat-tck repository to run the EL, Servlet, Pages and WebSocket TCKs once every day for all combinations of JDK 17 & 21, Ubuntu latest, MacOS latest and Windows latest using GitHub actions.

There were a few issues to iron out but these should now all be resolved.

The TCK will run at just after 08.00 UTC every day and it will use the latest Tomcat 11 SNAPSHOT (these are updated on every commit by buildbot).

Windows seems to take a little longer than the others but the full TCK run (all four TCKs) is complete in just under 25 minutes. Considering it used to take longer than that to run any of the old TCKs, kudos to the Jakarta EE folks that have been working on the refactoring.

Tomcat 11.0.x currently passes the TCK (as it should).

I have no plans to formally certify Tomcat as passing the TCK over and above what I have already completed as part of the release process for each of the specifications (the specification release process requires at least one compatible implementation).

Nice work.

My guess is that getting Tomcat to be formally-certified would take (1) money (2) politics and (3) other stuff nobody wants to deal with any time soon.

I wonder if we made it sooooo easy to certify (e.g. automated builds and automated TCK executions) that someone else might just do it for us (I'm looking at you, /Eclipse Foundation/.. I seem to remember a conference presentation about how important Tomcat was to Eclipse).

When the TCK runs, does it produce a report which includes the identities of the files that were used to run produce that report? Specifically, I'm wondering if the TCK report can be used to verify that a *specific release* has passed and TCK and that can be verified by an external observer.

I'm not volunteering to add TCK runs as part of the standard release process but if "anyone" could produce a TCK report which shows the entirely-reproducible build that is Tomcat x.y.z is what has been tested, that would be really great.

Instead of just "trust me, I ran it on my machine and this report says it passed", anyone could verify that the same artifacts we released were the ones the TCK was run on.

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to