Skip to content

Update jvm artifact deployment for new maven central portal #838

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

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

chippmann
Copy link
Contributor

This updates our jvm deployment plugin and ci/cd setup for the new maven central plugin portal as the old one is discontinued and we cannot publish updates anymore.

As there is no official gradle plugin yet to publish to the new plugin portal using gradle, this third party gradle plugin is used and configured instead as it's one ofe the mentioned third party alternatives in the official documentation.

Open tasks:

  • @piiertho Move the newly created secrets to org level (i do not have he rights to do so)
    • GODOT_KOTLIN_MAVEN_CENTRAL_PORTAL_TOKEN_PASSWORD
    • GODOT_KOTLIN_MAVEN_CENTRAL_PORTAL_TOKEN_USERNAME
  • Remove GODOT_KOTLIN_GPG_PRIVATE_KEY_ASCII and rename and move GODOT_KOTLIN_GPG_PRIVATE_KEY_ASCII_CLEANED to org level
    • This was needed as the old ASCII private key representation is/was malformed and the old setup could just handle that. But the new plugin cannot and expects a correctly formatted key. But this should only be done once we did at least one deployment with the new setup to ensure it's working correctly. Also if you @piiertho use this key in other repos as well, i would wait with the removal until you've migrated them as well.

@chippmann chippmann requested review from CedNaru and piiertho June 8, 2025 16:54
@chippmann
Copy link
Contributor Author

After this one is merged, we can setup the Snapshot repository as requested in #269

@tommyettinger
Copy link

Good choice on VannikTech as the plugin to use, it's been my go-to for Maven Central releases for a while now and the update to the new repo was fairly painless. It's certainly much faster to release now! I also had to generate new tokens in the Sonatype web UI, the old ones would not work for me. I know some stuff has changed since the initial news that we need to migrate, and I had migrated all my projects about a month ago, so my experience may not match yours.

- name: Setup publish gradle properties
shell: sh
run: |
echo "mavenCentralUsername=$GODOT_KOTLIN_MAVEN_CENTRAL_PORTAL_TOKEN_USERNAME" >> ~/.gradle/gradle.properties
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we write those to properties ?

@@ -13,10 +13,10 @@ on:
type: string

env:
GODOT_KOTLIN_GPG_PRIVATE_KEY_ASCII: ${{ secrets.GODOT_KOTLIN_GPG_PRIVATE_KEY_ASCII }}
GODOT_KOTLIN_GPG_PRIVATE_KEY_ASCII: ${{ secrets.GODOT_KOTLIN_GPG_PRIVATE_KEY_ASCII_CLEANED }} # TODO: remove old key and rename this one once we're sure that the new deployment works
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rename GODOT_KOTLIN prefix to UTOPIA_RISE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants