-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.x: Release to Sonatype directly #7181
Conversation
Codecov Report
@@ Coverage Diff @@
## 3.x #7181 +/- ##
============================================
- Coverage 99.56% 99.49% -0.07%
Complexity 6751 6751
============================================
Files 747 747
Lines 47350 47350
Branches 6367 6367
============================================
- Hits 47143 47113 -30
- Misses 94 105 +11
- Partials 113 132 +19 Continue to review full report at Codecov.
|
FYI default plugins shipped with gradle can do that without external dependencies - Just apply corresponding plugins on modules that need to be released - their publishing and signing configurations are rather tiny External config is
May be worth considering to reduce future maintenance burden. |
Update the release process to use Sonatype directly via the help of the
com.vanniktech:gradle-maven-publish-plugin
.In order for it to work, two secrets has to be set in the settings:
SIGNING_PRIVATE_KEY
SIGNING_PASSWORD
The
SIGNING_PRIVATE_KEY
should be the ascii-armored private key to sign the JAR files and can be generated from a pgp keychain:The
SIGNING_PASSWORD
is then the password for thatprivate_key.asc
.I tested the process on my local machine as much as I could, but we'll only know if it really works when doing an RxJava release.
Resolves #7179