[cdi-dev] Publishing the TCK

[Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>]

Hi,

When Emily was going to promote the CDI TCK for the 5.0 release, she discovered that the files were already there. It looks like the release script on your CI now uploads to the promoted location https://download.eclipse.org/jakartaee/ and not to https://download.eclipse.org/ee4j/ (see attached screenshot)

This in itself is not really an issue, but the problem comes when the Specification Committee runs the promotion job, it fails since the files are already there. 

One of the things the promotion job does is to sign the zip with the Jakarta EE Spec Cmte private key so it can be validated with the public key, https://raw.githubusercontent.com/jakartaee/specification-committee/master/jakartaee-spec-committee.pub. 

The signature produced by the CDI CI job is not the correct one, so anyone who tries to validate the signature tck will get an error. 

To fix this, we need you to:

1. Update the CI Job (change "jakartaee" to "ee4j" in the DOWNLOAD_DIR variable)

2. Run the job again

3. Notify us (Emily and me), so we can remove the published artifacts and run our job to generate the correct signature and copy the artifact over to the jakartaee download area.

NOTE! This only applies to the 5.0 release.

Ivar

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

Attachment: Screenshot 2026-09-22 at 14.20.59.png
Description: PNG image