Repository navigation
ci: publish to Maven Central without a manual click - #2
Merged
Merged
Conversation
The central-publishing plugin leaves a deployment in the portal as "validated" and waits for someone to press Publish. A release here is already gated on a green suite and on the tag matching the version, so that click is a place to forget rather than a decision. autoPublish takes it, and waitUntil=published makes the build fail when the portal rejects the deployment instead of reporting success on something stuck. Adds the same tag-versus-version gate the other SDKs now carry. Maven Central never lets a version be replaced.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
autoPublish. The central-publishing plugin otherwise leaves a deployment in the portal as validated and waits for someone to press Publish. A release here is already gated on a green suite and on the tag matching the version, so that click is a place to forget rather than a decision.waitUntil=published. Without it the build reports success as soon as the upload is accepted, and a deployment the portal later rejects sits there silently. Now the build fails with it.The version gate, like the other SDKs: the job refuses a tag that disagrees with
project.version. Maven Central never lets a version be replaced.The
pom.xmlwas already complete for Central:name,description,url,licenses,developers,scm, plus the sources and javadoc plugins and GPG signing in thereleaseprofile.Still needed before this can run (the heavy part of Maven Central, all on your side):
com.camelmailer, then publish the verification code it gives you as a DNS TXT record oncamelmailer.comand hit Verify.MAVEN_CENTRAL_USERNAME,MAVEN_CENTRAL_PASSWORD(a portal user token, not your login),MAVEN_GPG_PRIVATE_KEY(the full ASCII-armoured block),MAVEN_GPG_PASSPHRASE.