CI: sign and publish from Jenkins, not GitHub Actions - #53
Merged
Conversation
The signing keys cannot leave the nShield HSM, so no PGP key or Central credential can live in a GitHub secret. Drop the workflow's publish job and Gradle's in-memory PGP signing: GitHub Actions builds the per-arch bundles, Jenkins signs and uploads them. Publishing now always stages to a local directory, since Central takes releases as a bundle rather than a maven deploy, and staging snapshots too keeps them from skipping PGP signing. Also fix the groupId to the registered namespace org.openssl.jostle and restore -sources/-javadoc to release builds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
quarckster
force-pushed
the
ci/publish-from-jenkins
branch
from
August 7, 2026 11:40
493ae58 to
4c40481
Compare
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
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.
The signing keys cannot leave the HSM, so no PGP key or Central credential can live in a GitHub secret. Drop the workflow's publish job and Gradle's in-memory PGP signing: GitHub Actions builds the per-arch bundles, OpenSSL signing infrastructure signs and uploads them.
Publishing now always stages to a local directory, since Central takes releases as a bundle rather than a maven deploy, and staging snapshots too keeps them from skipping PGP signing. Also fix the groupId to the registered namespace org.openssl.jostle and restore -sources/-javadoc to release builds.