The Eclipse Dataspace Connector project want to publish artifacts that can be retrieved from Maven central. What needs to be done, what (intermediary) repo must created for publication? Especially it is a question of how to get the corresponding credentials that we can store as repo secret? Aim is to enable a Github workflow or job to publish SNAPHOTS, triggered by PR merges into main.
Do we need a Jenkins instance as a first step? Are there other ways to achieve this?
To simplify setting up jobs on our cluster-based infra, we provide a pod template that can also be used with freestyle jobs. The pod template has the label "centos-7" which can be specified in the job configuration under "Restrict where this project can be run". The image contains more commonly used dependencies than the default “basic” pod template.
@fgurr sorry to reopen the issue here. Would it be possible that I can get your support on how to create the token via nexus repository manager? Also I need rights to add secrets in our Github-Repo to configure an artifact publication. Can we have a chat or call?
We have made another attempt to move forward from the previous information and links. Unfortunately, we have not yet succeeded in making progress here, as some points and how they are intended at EF are not clear to us. Any chance to have a short call to clarify things?
16:54:17 + gpg --batch --import ****
16:54:17 gpg: directory '/home/jenkins/.gnupg' created
16:54:17 gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
16:54:17 gpg: no valid OpenPGP data found.
Difference to the picture in linked wiki page is the inactive button on the right to "secret-subkeys.asc" textfield. We tried to echo the gpg-key but this is (intentional) masked.
AFAICT, you are still missing the deploy part in your Gradle build.
I'm not a SME for Gradle, but I think there is a way to read the deploy credentials from the default Maven settings.xml file. Alternatively, we can also create the credentials in a gradle.properties file if that's easier.