Closed klu2 closed 1 year ago
Gradle:
Class-Path
gradle build
I'd also recommend you to use in-memory ascii-armored keys on the CI server as explained https://docs.gradle.org/current/userguide/signing_plugin.html#sec:in-memory-keys. You can have a look at https://github.com/cloudflightio/json-wrapper/blob/master/build.gradle.kts#L97 how I did that in another repository, just pass the PGP_SECRET and PGP_PASSPHRASE as environment variables then.
Gitlab Actions:
I'd also recommend you to create a separate GitHub Action Pipeline to push to maven central directly by creating a Release here on GitHub, see https://github.com/cloudflightio/json-wrapper/blob/master/.github/workflows/github-publish.yml
Gradle:
Class-Path
to the JAR manifestgradle build
locallyI'd also recommend you to use in-memory ascii-armored keys on the CI server as explained https://docs.gradle.org/current/userguide/signing_plugin.html#sec:in-memory-keys. You can have a look at https://github.com/cloudflightio/json-wrapper/blob/master/build.gradle.kts#L97 how I did that in another repository, just pass the PGP_SECRET and PGP_PASSPHRASE as environment variables then.
Gitlab Actions:
I'd also recommend you to create a separate GitHub Action Pipeline to push to maven central directly by creating a Release here on GitHub, see https://github.com/cloudflightio/json-wrapper/blob/master/.github/workflows/github-publish.yml