Jenkins ee4j.data cannot import gpg keyring

Summary

When attempting to push a release to staging we need to import the GPG keys to sign the release. The keyring file exists, but we get an error when we try to import it.

gpg --batch --import ****
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

This error seems to have started approx 10-15 days ago.

Steps to reproduce

This can be replicated by running the following jenkins job: https://ci.eclipse.org/data/view/CI%20Builds/job/jakarta-data-deploy/

What is the current bug behavior?

GPG attempt to import the subkey, but fails. Likely the keyring file is empty, corrupted, or malformed.

What is the expected correct behavior?

We should have a valid GPG formatted keyring that allows us to sign artifacts.

Relevant logs and/or screenshots

See summary

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

We are working on publishing a service release for Jakarta Data and this is blocking our ability to do so.