Skip to content

Migrate from OSSRH service to Central Publisher Portal #140

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

Closed
ppatierno opened this issue May 28, 2025 · 0 comments · Fixed by #141
Closed

Migrate from OSSRH service to Central Publisher Portal #140

ppatierno opened this issue May 28, 2025 · 0 comments · Fixed by #141
Assignees

Comments

@ppatierno
Copy link
Member

The OSSRH service we use for pushing the artifacts withing Nexus repository manager will reach end-of-life on June 30th, 2025. They have the announcement when you log into the legacy service we use right now. We should migrate to the new one which can be done through the Central support. More details here https://central.sonatype.org/news/20250326_ossrh_sunset/

The main changes to make at project level are:

  • replacing the nexus-staging-maven-plugin with the central-publishing-maven-plugin (more info about the new plugin here)
  • removing the snapshotRepository
  • updating the Azure scrips settings.xml and the corresponding job to deploy Strimzi artifacts

An example of migration can be found here

The migration of the io.strimzi namespace together with the generation of the new CENTRAL_USERNAME and CENTRAL_PASSWORD (using token generation feature) are not in the scope of this issue.
We'll do them out of band together with updating the Azure pipelines configuration within the Azure portal.

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 a pull request may close this issue.

1 participant