Sample configuration for singing and publishing to maven central #710
+40
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a sample configuration to implement signing and publishing to maven central using a buildkite pipeline.
Note: The script will only work in buildkite. It will work as-it is without any changes there.
It's recomended to change use the https://github.com/elastic/vault-secrets-buildkite-plugin in the pipeline instead of the vault cli in the script.
I tested the signing locally and it works, the publishing fails with:
But I tested that the credentials are passed correctly.
It most likeley fails because not all requirements are ment, see: https://central.sonatype.org/publish/requirements/
You can compare the example pom with yours and lookg at the other requirements. At least the javadoc and source jars are missing.