From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

would `@Internal` properties on the tasks bound to each other be the way to do this?

The scope of a shared build service is the current build run, so yes, you can even share data from the settings script to the build scripts with them, without using the dreaded extra properties.

How to properly share the data probably depends on many factors.
One way could also be to have in the shared service a map with the project path as key for example to "namespace" the data.

ok. in this case, i think linking properties on the tasks will be simpler. i just needed the confirmation that the build service is global. that is good to know, i will have other use cases for that. Thanks!

Just to clarify: build services are currently only build scoped, but they could certainly be supported at the project level, or any scope really, if people have use cases for this. Feel free to raise a feature request for this.

I indeed had a use-case for a project scoped build service last week. I simply solved it by using the project path in the service name. Maybe I'll send a feature request.

I reported it at <https://github.com/gradle/gradle/issues/27756>