Indeed, the TCK was executed against 4.0.3, which is in the output of the job log:
+ cd /home/jenkins/workspace/2_servlet-run-tck-against-staged-build/download
+ wget -q https://oss.sonatype.org/content/repositories/staging/jakarta/servlet/jakarta.servlet-api/4.0.3/jakarta.servlet-api-4.0.3.jar -O jakarta.servlet-api.jar
4.0.3 was build from 95f4fbcb0fe1b4d95a6bebbaeda69c811ca5739e
Checking out Revision 95f4fbcb0fe1b4d95a6bebbaeda69c811ca5739e (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 95f4fbcb0fe1b4d95a6bebbaeda69c811ca5739e
Which was staged in 6ed830e58a2d9e
[INFO] Installing /home/jenkins/workspace/1_servlet-build-and-stage/api/target/jakarta.servlet-api-4.0.3-javadoc.jar.asc to /home/jenkins/workspace/1_servlet-build-and-stage/api/target/nexus-staging/staging/6ed830e58a2d9e/jakarta/servlet/jakarta.servlet-api/4.0.3/jakarta.servlet-api-4.0.3-javadoc.jar.asc
[INFO] Performing remote staging...
[INFO]
[INFO] * Remote staging into staging profile ID "6ed830e58a2d9e"
[INFO] * Created staging repository with ID "jakartaservlet-1011".
The test run for that were:
[javatest.batch] Number of Tests Passed = 1689
[javatest.batch] Number of Tests Failed = 0
[javatest.batch] Number of Tests with Errors = 0
[javatest.batch] ********************************************************************************
Not sure why/if/how the signature tests didn't run.
Kind regards,
Arjan