Allow publishing to a pre-defined staging repository

Author: IgnatBeresnev

build-logic/src/main/kotlin/dokkabuild.publish-base.gradle.kts

@@ -1,3 +1,5 @@
+import java.net.URI
+
 /*
 * Copyright 2014-2023 JetBrains s.r.o. Use of this source code is governed by the Apache 2.0 license.
 */
@@ -11,7 +13,7 @@ publishing {
     repositories {
         maven {
             name = "mavenCentral"
-            url = uri("https://oss.sonatype.org/service/local/staging/deploy/maven2/")
+            url = mavenCentralRepositoryUri()
             credentials {
                 username = System.getenv("DOKKA_SONATYPE_USER")
                 password = System.getenv("DOKKA_SONATYPE_PASSWORD")
@@ -73,6 +75,20 @@ publishing {
     }
 }
 
+/**
+ * Due to Gradle running publishing tasks in parallel, multiple staging repositories
+ * can be created within a couple of seconds with artifact files scattered throughout.
+ * The safest and most stable option is to publish to a pre-defined staging repository.
+ */
+fun mavenCentralRepositoryUri(): URI {
+    val repositoryId: String? = System.getenv("DOKKA_MVN_CENTRAL_REPOSITORY_ID")
+    return if (repositoryId == null) {
+        URI("https://oss.sonatype.org/service/local/staging/deploy/maven2/")
+    } else {
+        URI("https://oss.sonatype.org/service/local/staging/deployByRepositoryId/$repositoryId")
+    }
+}
+
 signing {
     useInMemoryPgpKeys(
         System.getenv("DOKKA_SIGN_KEY_ID")?.takeIf(String::isNotBlank),