Update the release plugin to use the central publishing API directly #3710
+61
−38
Conversation
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
Following the recommendation of the central publishing portal, this updates our publishing plugin from Nexus to jReleaser. See: https://central.sonatype.org/publish/publish-portal-gradle/ The way that this works is that now, the "publish" command will publish artifacts locally to a staging repository that is in the build directory. At the conclusion of the build, the `jreleaserDeploy` task will take those artifacts and send them up to maven central. It will sign them before it does so, which is why this also removes the manual signing configuration that we'd previously had in our `publishing.gradle` configuration. I've tested this out by applying these changes to a parallel repo I had. I was even able to validate that it could deploy to maven central, but I had configured that other repo to only uplaod artifacts. This is supposed to both upload and then publish the artifacts in the "deploy" step. I have not been able to actually validate that that worked, for obvious reasons. I can see locally that when I call `publish`, it publishes to a staging folder in the build directory. This resolves FoundationDB#3709.
ScottDugas
requested changes
Nov 3, 2025
ScottDugas
approved these changes
Nov 3, 2025
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this pull request
Nov 4, 2025
…irectly (FoundationDB#3710)" This reverts commit b1dac67.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Following the recommendation of the central publishing portal, this updates our publishing plugin from Nexus to jReleaser. See: https://central.sonatype.org/publish/publish-portal-gradle/
The way that this works is that now, the "publish" command will publish artifacts locally to a staging repository that is in the build directory. At the conclusion of the build, the
jreleaserDeploytask will take those artifacts and send them up to maven central. It will sign them before it does so, which is why this also removes the manual signing configuration that we'd previously had in ourpublishing.gradleconfiguration.I've tested this out by applying these changes to a parallel repo I had. I was even able to validate that it could deploy to maven central, but I had configured that other repo to only uplaod artifacts. This is supposed to both upload and then publish the artifacts in the "deploy" step. I have not been able to actually validate that that worked, for obvious reasons. I can see locally that when I call
publish, it publishes to a staging folder in the build directory.This resolves #3709.