This message was deleted.

Actually the

OperationCompletionListener

in combination with a shared build service is already also a way to get build finished event CC compatibly. You make it implement

AutoCloseable

and do the build finished action in the

close

method. It will be invoked between the last task finished and the build finished. The

FlowAction

is something new that probably has some potential to develop.

Interesting. Though I’m curious if the

FlowAction

executes after the configuration cache is stored, making it the latest possible event that can be subscribed to. It would then also include a information on a failure storing the configuration cache. My understanding is that a failure in storing the configuration cache wouldn’t be passed to the

OperationCompletionListener

.

Well, try it out. 🙂 Just make a print statement and see whether it comes after "cc entry stored" or not. But whether it would then also get the info that storing failed is worth another test. 🙂

I stopped being lazy and did the test 🙂. “Configuration cach entry stored” was printed below the print statements for both the

execute

of the

FlowAction

as well as the

close

of the

AutoClosable OperationCompletionListener

. In conclusion it seems like these two APIs are almost completely overlapping. It’s a bit confusing, I’m even finding myself mixing them up!