This message was deleted.

One of the use cases we have is building a kotlin multiplatform project on different hosts (e.g. jvm, windows, linux, macos, js) and then publishing everything all together after we know everything built successfully. The only alternative I see is publish to a nexus staging repo and only release it after everything succeeds but I'd like to understand if there is a way to re-use gradle maven publishing infrastructrure without going down that road.

Hi Aaron 👋 I don’t know specifics, but I would try to explore the tasks involved in publishing. Then I would try to create a custom task or extension that will deliver as outputs the files we need to pass to the publishing task and then configure latest to consume the inputs.

// pseudo code
interface MyExtension {
   @get:Input
   val artifactsDir: RegularFileProperty

}

myExtension {
  artifactsDir = file("/some/path/to/local/dir")
}

val myExtension = project.extensions.findByName("myExtension")
// we need to sneak peek into impl of the publish plugin to figure out the publishing task type
val customPublications = project.register<PublishTask>(name = "republish") {
  artifactSource.set(myExtension.artifactsDir)
}

Or maybe it is already enough to use a build cache / remote build cache, so that results of time-consuming cacheable tasks can be reused to not "re-build the world"

Or maybe it is already enough to use a build cache / remote build cache, so that results of time-consuming cacheable tasks can be reused to not "re-build the world"

This is actually what we do now but I don't think it will work when we flip on support for other KMP targets other than JVM.

KGP supports build cache, and if not, it would be easier to file a bug that looking for a workaround

thanks for chiming in, we have a few constraints to deal with. (1) We build and publish on totally separate hosts. (2) we would like to build separate KMP targets in parallel on different hosts and then combine the artifacts and publish them once all target platforms are built.

I am not sure then if remote build cache could help here, I haven't played with it. What is the reason of that split? Very large library?