Credentials for Develocity setup of the GlassFish project

Summary

• See https://github.com/eclipse-ee4j/glassfish/pull/25324 , unfortunately we merget it too early and now the build of GlassFish is impossible.

Steps to reproduce

Crate a PR for Eclipse GlassFish - and it will fail the build on Jenkins CI.

What is the current bug behavior?

See https://ci.eclipse.org/glassfish/job/glassfish_build-and-test-using-jenkinsfile/job/PR-25291/12/console as an example. After merging https://github.com/eclipse-ee4j/glassfish/pull/25324 we cannot build any PR.

Also:   org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 650afe83-a91b-4624-a7a8-d11ea71bba53
com.datapipe.jenkins.vault.exception.VaultPluginException: The vault url was not configured - please specify the vault url to use.
	at PluginClassLoader for hashicorp-vault-plugin//com.datapipe.jenkins.vault.VaultAccessor.retrieveVaultSecrets(VaultAccessor.java:181)
	at PluginClassLoader for hashicorp-vault-plugin//com.datapipe.jenkins.vault.VaultBindingStep$Execution.doStart(VaultBindingStep.java:115)
	at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:857)

GitHub has been notified of this commit’s build result

Finished: FAILURE

What is the expected correct behavior?

Building the PR, running tests, etc.

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

The development of GlassFish is blocked by this. We can always revert develocity related changes, but we would like to give it a chance to resolve issues first.