Failed to findSonatypeStagingRepository with the new configured URL to maven Portal

[abdelhak-cs]

After the migration to the new Maven Portal URL's , it fails to deploy if the invocation are separated :

val nexusStagingRepoURL = "https://ossrh-staging-api.central.sonatype.com/service/local/"
val nexusSnapshotRepoURL = "https://central.sonatype.com/repository/maven-snapshots/"
nexusPublishing {
    // Set the description of the staging repository.
    repositoryDescription = project.getString("VERSION_NAME")
    repositories {
        sonatype {
            stagingProfileId = nexusProfileId
            nexusUrl.set(uri(nexusStagingRepoURL))
            snapshotRepositoryUrl.set(uri(nexusSnapshotRepoURL))
            username.set(nexusUsername)
            password.set(nexusPassword)
        }
    }
}

./gradlew publishMavenPublicationToSonatypeRepository closeSonatypeStagingRepository => Success

Task :initializeSonatypeStagingRepository
Created staging repository '**********--fb701b88-69b6-41c3-a547-c2357b085058' at https://ossrh-staging-api.central.sonatype.com/service/local/repositories/***********--fb701b88-69b6-41c3-a547-c2357b085058/content/

./gradlew findSonatypeStagingRepository releaseSonatypeStagingRepository

FAILURE: Build failed with an exception.
Execution failed for task ':findSonatypeStagingRepository'.
Failed to find staging repository, stagingProfileId: , server at https://ossrh-staging-api.central.sonatype.com/service/local/ responded with status code 400, body: Endpoint /service/local/staging/profile_repositories/ not supported. Please contact Central Support (central-support@sonatype.com)

[szpak]

Have you migrated your "namespace"?

[abdelhak-cs]

Yes the "namespace" is migrated.
i success to deploy to it if i invoke everything in one command means:
./gradlew publishMavenPublicationToSonatypeRepository closeSonatypeStagingRepository

but will fail if :

1. ./gradlew publishMavenPublicationToSonatypeRepository
2. ./gradlew findSonatypeStagingRepository closeSonatypeStagingRepository

[szpak]

Good to know that it fails only in the second case. There's might be something with find* in the new API.

In fact, re-reading your message, the error states it clear :)

status code 400, body: Endpoint /service/local/staging/profile_repositories/ not supported

That endpoint is not supported in the new solution. When you use it in the same call, Gradle/Plugin keeps the number and can reuse it without asking server.

[louwers]

Having this same issue.

What am I supposed to set as stagingProfileId after migration?

[Belak-Ghouas]

I think for now findStagingRepository will fail, since doesn’t support the new endpoint used to find staging repositories.

What does work for now is invoking all commands at once, like:
./gradlew publishMavenPublicationToSonatypeRepository closeSonatypeStagingRepository releaseSonatypeStagingRepository

Or alternatively:

./gradlew publishMavenPublicationToSonatypeRepository closeSonatypeStagingRepository

...and then doing the release manually from the Maven portal.

[szpak]

Exactly, Belak-Ghouas. @louwers You need to call publishing with close/release in the same command.

Alternatively, you might manually (as API doesn't seem to support that) get the stagingRepositoryId from UI and pass it as a parameter --staging-repository-id=...

[louwers]

Thanks for your reply. Where in the UI can I find it?

[amy-keibler]

Hey, y'all. Dropping in from the Maven Central team to let you know that we've added support for the endpoint that is called by findSonatypeStagingRepository and added support for the repository description after reading the plugin and determining that that was necessary as well.

Currently, this still is limited by expecting all requests to come from the same IP, so if you need to make requests from other IPs, you'll still need to call the corresponding manual endpoint in order for the repository to be closed and uploaded to the Central Publisher Portal.

If you encounter any issues, please don't hesitate to reach out via the the Central Support Email.

[szpak]

Great news! Thanks @amy-keibler for the update.
@abdelhak-cs @louwers Has it solved the problem you had?

[cortinico]

@szpak can we update the description on the README here https://github.com/gradle-nexus/publish-plugin#publishing-and-closing-in-different-gradle-invocations mentioning that this feature is actually broken with Central Portal?

[szpak]

@szpak can we update the description on the README here https://github.com/gradle-nexus/publish-plugin#publishing-and-closing-in-different-gradle-invocations mentioning that this feature is actually broken with Central Portal?

@cortinico Maybe to add a note about a need to use the same IP (as I understood Amy correctly)?

[cortinico]

It's unclear what's the status of this feature to me. I think someone should do some manual testing to verify what works and what not.

We were using findSonatypeStagingRepository as part of the React Native GitHub Actions workflow which is quite complicated. We had to revert to invoke ./gradlew publishToSonatype closeAndReleaseSonatypeStagingRepository because any other combination won't work.

I've attempted to:

1. Invoke publishToSonatype and then find...Repository closeAndRelease...Repository
2. Invoke publishToSonatype close...Repository and then find...Repository release...Repository
   but both are failing at the find step.

Maybe to add a note about a need to use the same IP (as I understood Amy correctly)?

@amy-keibler this is confusing to me. Why would we need to use the same IP address? This is extremely restrictive and makes it really hard to integrate this workflow inside CIs as IP addresses could change between runners.

The whole point of using find... is to be able to publish artifacts and release them in different moments.