yuqi1129 commented on PR #4475: URL: https://github.com/apache/gravitino/pull/4475#issuecomment-2287682494
@jerryshao I have tried several times, and we could not find a solution to resolve the multiple-repositories problem temporarily. I reported this issue to the ASF, see: https://issues.apache.org/jira/browse/INFRA-26022 besides, I tried a different approach similar to how we publish to [Sonatype](https://s01.oss.sonatype.org/service/local/). ```kotlin nexusPublishing { repositories { create("apache") { val snapshot = uri("https://repository.apache.org/content/repositories/snapshots/") val release = uri("https://repository.apache.org/service/local/staging/deploy/maven2/") nexusUrl.set(release) snapshotRepositoryUrl.set(snapshot) username.set(System.getenv("APACHE_USERNAME")) password.set(System.getenv("APACHE_PASSWORD")) stagingProfileId.set("170bb01395e84a") } } } packageGroup.set("org.apache.gravitino") } ``` However, publishing the snapshot jars to the apache repository is okay, it still have problem in publishing to the release repository. The problem is as below: ``` Execution failed for task ':initializeApacheStagingRepository'. > Failed to create staging repository, server at https://repository.apache.org/service/local/staging/deploy/maven2/ responded with status code 400, body: <html> <head> <title>400 - Bad Request</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link rel="icon" type="image/png" href="https://repository.apache.org/favicon.png"> <!--[if IE]> <link rel="SHORTCUT ICON" href="https://repository.apache.org/favicon.ico"/> <![endif]--> <link rel="stylesheet" href="https://repository.apache.org/static/css/Sonatype-content.css?2.14.20-02" type="text/css" media="screen" title="no title" charset="utf-8"> </head> <body> <h1>400 - Bad Request</h1> <p>Cannot find a matching staging profile</p> </body> </html> ``` I am 100% certain that the staging profile ID is correct and there is no possible explanation for the error. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
