Republishing to Nexus in case of no new commits

Republishing to Nexus in case of no new commits

[ajoberstar]

The gradle-git plugin doesn't provide anything for publishing, so I'm not sure there's anything that could be done here. There's a prepare task and a release task that cover the Git tag/push. But besides that, the plugin relies on the user adding dependencies on other tasks they want included in the release.

Let me know if I'm misunderstanding what you're looking for.

Maybe then my setup is wrong. Basically what I want to prevent is the republishing of already released versions. Somehow as I see it, the release task could remove all tasks that depend on it from the taskgraph to prevent them from being executed in case there is nothing new to be released, but that may not be a recommended Gradle solution. Which solution could you recommend to avoid the republishing scenario? Op 28 sep. 2017 03:21 schreef "Andrew Oberstar" <[email protected]>: The gradle-git plugin doesn't provide anything for publishing, so I'm not sure there's anything that could be done here. There's a prepare task and a release task that cover the Git tag/push. But besides that, the plugin relies on the user adding dependencies on other tasks they want included in the release. Let me know if I'm misunderstanding what you're looking for. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#269 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJWmxdz02JUbqmEa2sZ_NzZWyUjVbkrNks5smvSOgaJpZM4PmPIm> .

Maybe an up-to-date when head is tagged with a version compatible with the release context? Op 28 sep. 2017 03:21 schreef "Andrew Oberstar" <[email protected]>:

…

The gradle-git plugin doesn't provide anything for publishing, so I'm not sure there's anything that could be done here. There's a prepare task and a release task that cover the Git tag/push. But besides that, the plugin relies on the user adding dependencies on other tasks they want included in the release. Let me know if I'm misunderstanding what you're looking for. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#269 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJWmxdz02JUbqmEa2sZ_NzZWyUjVbkrNks5smvSOgaJpZM4PmPIm> .

[ajoberstar]

You could add an onlyIf check on the tasks you don't want rerun that would check if the project version already has a tag. I don't think this is a good general solution, but may work for what you're describing.

As for any changes in gradle-git itself, given the status of the project (see the readme), I won't be doing anything more than bug fixes.