Please support multi-project publishing

[Vampire]

I have a root project and two sub-modules in the same GitHub repo.
If I apply the plugin to all projects, it fails because of "release does already exist".
Of course I can only apply the plugin to the root project and collect the artifacts to be published there, but it would of course be nice if this just worked if possible. :-)

[Larusso]

Hmm never had this setup in mind. But I will try and play around and see how hard it is to support.

[Vampire]

Maybe it is sufficient to be able to configure whether an existing tag should fail the build or add the files or something like that.

[Vampire]

Actually I'm happy with how I have it now, with from allprojects.configurations.archives.artifacts.files and only applied to root project.

[Larusso]

I had in mind to reference configurations:

atlas-github/src/integrationTest/groovy/wooga/gradle/github/GithubPublishAssetsIntegrationSpec.groovy

Lines 93 to 132 in 9d31fe5

	def "publish files from configurations"() {
	given: "a few files"
	createFile("fileToPublish1.json") << "test content"
	createFile("fileToPublish2.json") << "test content"
	createFile("fileToPublish3.json") << "test content"
	createFile("fileToPublish4.json") << "test content"
	and: "a buildfile with publish task and custom configuration"
	buildFile << """
	configurations {
	githubAssets
	}
	dependencies {
	githubAssets files("fileToPublish1.json")
	githubAssets files("fileToPublish2.json")
	githubAssets files("fileToPublish3.json")
	githubAssets files("fileToPublish4.json")
	}
	task testPublish(type:wooga.gradle.github.publish.tasks.GithubPublish) {
	from configurations.githubAssets
	tagName = "$tagName"
	}
	"""
	when:
	runTasksSuccessfully("testPublish")
	then:
	def release = getRelease(tagName)
	!release.isDraft()
	def assets = release.assets
	assets.size() == 4
	assets.every() { it.name =~ /fileToPublish\d\.json/ }
	where:
	tagName = "v0.3.0-GithubPublishAssetsIntegrationSpec"
	}

I have no test with a multi project setup at the moment. I should add this because configuration and artifact handling is a little bit fuzzy on my part.

But like in the test you could define dependencies to the sub project configuration or fileTree's

Updating Releases is on my roadmap but I had no real use case.

[Vampire]

Yeah, seen this in the docs, but I've seen no point in declaring my artifacts again, when what I want to publish is already defined as artifacts for the archives configuration as shown in my example. You could add a test for that though.

[Larusso]

OK. from allprojects.configurations.archives.artifacts.files but this means really every sub project. But since GithubPublish is just a CopySpec all kind of configuration incantations should work. But I will add a spec for your multi project usecase and add an entry in the docs.

[Vampire]

Yes, in my case this is exactly what I wanted and yes, being a CopySpec is good for flexibility :-)