This message was deleted.

afaik your best option for passing data between tasks is via output files or directories that gradle can track

@Lars Ködderitzsch workers with no isolation can spawn other work actions, but workers with other isolation modes can’t. See https://github.com/gradle/gradle/blob/6134a82a9d34dea219fc01cfb330f28dd88aa199/subprojects/workers/src/integTest/groovy/org/gradle/workers/internal/WorkerExecutorNestingIntegrationTest.groovy#L106 and other test cases in that class Using files is one way. You pass the path to outputs to your first action with classloader isolation, submit it, wait for it and then submit the other one passing the paths. Depending on your use case you could instead use no isolation by passing the classpath as a parameter to your first action. Then you can spawn another from it.

@Paul Merlin thanks, I'll use an intermediary file then to funnel the data to the second worker. Is there a benefit from using property/lazy types in worker params or is it just convenience to connect them from the task properties more easily?

It is mostly good for convenience and uniformity. Worker parameters are realized before being passed to the worker anyway.