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
Move away from Bintray #435
Comments
https://github.com/gradle-nexus/publish-plugin/ might be a good solution, as this seems to do all the necessary steps. i will investigate further into this |
based on @nipafx link in discord (https://github.com/rwinch/gradle-publish-ossrh-sample) - we should evaluate if we need signing, yes it is a security feature and surely nice to have, but is it needed. We could start with this as our first iteration and add signing at a later stage |
NB: The credentials for the Nexus token and the PGP key are now organization secrets, so other projects can access them as well if they're added to the list of projects that they're shared with. |
With Bintray closing for new uploads soon[1], we recofnigured the build to release to Sonatype's Nexus aka "Maven Central" directly. That meant: * replacing Gradle plugin _com.jfrog.bintray_ with _io.github.gradle-nexus.publish-plugin_ [2] * adding a PGP key for signing as a secrets (`JUNIT_PIONEER_PGP_...`) We took the opportunity to make the new secrets as well as the Nexus credentials organization secrets (as opposed to just the project). [1] https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ [2] https://docs.gradle.org/current/userguide/signing_plugin.html
A few loosely related changes that finish the release process update: * adds `GITHUB_TOKEN` to `release-build.yml` (was erroneously removed in #463) * removes `docs/release-notes.md` and updates the documentation accordingly because Shipkit no longer writes release notes * removes all mentions of JCenter and Bintray Unrelated, this change replaces links to codefx.org with nipafx.dev. Related to: #435, #442
Bintray gets shut down on May 1st, so we need to move away from it. I think it would be a good idea to see what other Shipkit-based projects do.
The text was updated successfully, but these errors were encountered: