Building requires a valid gpg configuration #20
Assignees
Labels
bug
Something isn't working
Comments
Merged
chriswk
pushed a commit
that referenced
this issue
Jan 2, 2023
This makes sure we only run nexus-staging and gpg plugin when actually running with the release profile active. We've configured the release plugin to run with the release profile active when running release:prepare/release:perform tasks. Fixes: #20
Merged
praveenpg
pushed a commit
that referenced
this issue
Jan 18, 2023
* fix: Add release profile This makes sure we only run nexus-staging and gpg plugin when actually running with the release profile active. We've configured the release plugin to run with the release profile active when running release:prepare/release:perform tasks. Fixes: #20 * fix: set to SNAPSHOT version again
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When building (particularly for PRs) our current maven setup requires a valid gpg/pgp setup in order for the build to sign the artifacts. Signing the artifacts when building/verifying CI seems excessive
Steps to reproduce the bug
Expected behavior
Build succeeds
Logs, error output, etc.
No response
Screenshots
No response
Additional context
Due to how our section in the pom is setup we require the maven gpg plugin to sign all artifacts also when not running with release profile. We should move this to a release profile, to ensure that we only sign artifacts when actually producting something to upload to maven central
Unleash version
No response
Subscription type
None
Hosting type
None
SDK information (language and version)
No response
The text was updated successfully, but these errors were encountered: