Skip to content

The jakartaee-tck ci environment seems to be missing secret-subkeys.asc configuration

Summary

I tried to create a new release job to create a new maven plugin artifact for the Jakarta EE TCK project and the job can be found here: https://ci.eclipse.org/jakartaee-tck/job/SigtestPluginRelease/

In the secret file binding section there is no option for selecting a secret-subkeys.asc file like I see on other Jakarta project CI jobs. Is this something that needs to be setup still?

Steps to reproduce

Look at the https://ci.eclipse.org/jakartaee-tck/job/SigtestPluginRelease/ and try to set the value for the KEYRING secret binding.

What is the current bug behavior?

There are no valued available in the Credentials drop down menu.

What is the expected correct behavior?

There should be a secret-subkeys.asc in the Credentials drop down menu.

Relevant logs and/or screenshots

The attached image shows the build environment bindings section of the job configuration.

Bindings

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • [] Major
  • Normal
  • Low

Impact

We have releases due in the next month that need a release of the signature test plugin.