ci.eclipse.org/el picking up wrong GPG keyring

Summary

Jenkins build jobs on ci.eclipse.org/el are picking up the wrong GPG keyring

Steps to reproduce

Run the expression-language-master-SNAPSHOT builds

What is the current bug behavior?

The build logs show GPG signing picking up the key for Eclipse Project for Concurrency Utilities cu-dev@eclipse.org and GPG signing fails.

What is the expected correct behavior?

KEYRING secret should point to the Expression Language specific GPG key and GPG signing succeeds.

Relevant logs and/or screenshots

+ gpg --batch --import ****
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: key F84B009E70DD1139: 1 signature not checked due to a missing key
gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created
gpg: key F84B009E70DD1139: public key "Eclipse Project for Concurrency Utilities <cu-dev@eclipse.org>" imported

For full logs see https://ci.eclipse.org/el/job/expression-language-master-SNAPSHOT/3/console

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

This is preventing me from producing a SNAPSHOT release for Expression Language. Jakarta projects have been requested to provide SNAPSHOT builds by 13th Oct although that deadline is somewhat arbitrary.