This message was deleted.

I have no idea, never used S3. But what I can say is that

finalizedBy

is proabably a bad idea. It is executed always, even if the publish task failed. If you need to do the custom work, you probably better add a

doLast { ... }

action to the existing task that publishes the file, so that it is done as additional action if it otherwise was successful already.

Oh shit, I had no idea finalizedBy had that behaviour. Does dependsOn do that? If B depends on A, B will get skipped if A fails, yea?

Yes, actually you could probably also make it

dependsOn

and

finalizedBy

. Then it should be automatically triggered, but only if it was successful.

The dependsOn and finalizedBy duality sounds like a bit of a hack to get that behaviour. I think in this case doLast is 100% the way to go. No need to add to the task graph if not really needed.

a few ideas: 1. unclear whether there is a readily available hook for ‘onPublish’ to then perform tagging - perhaps a wander through the Gradle source may help there; 2. Add S3 event handler lambda to catch each artifact as it’s provided and add tags (this may not be feasible as the context for tagging is limited to the key)

back to the original question: there is currently no hooks to modify publishing remote calls. Though this is a request we have seen in the past.