This message was deleted.

The main point is declare really everything what can influence task result as input, ideally by provider.

That is more for task up-to-dateness and task output cacheability. For configuration cache, you just are not allowed to do certain things at execution time like accessing the

project

or having things as properties that Gradle cannot serialize into the configuration cache.

It is possible to create a POJO class and which will contain all required data?

yeah, it should be, if it is either a Gradle managed type or it implements

java.io.Serializable

https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:not_yet_implemented:java_serialization Just make sure to annotate the task properties in the POJO with the correct task input/output types, and use

@Nested

when it’s a task property To reduce the duplication if you have lots of different specific task types, then you could create some custom task type for all your tasks, and define the POJO as a property

abstract class MyBaseTaskType : DefaultTask() {
  @get:Nested 
  abstract val myCommonData: Property<MyCommonData>
}

and then in the plugin you can configure all tasks by type, and add the data - then it’s just done in one place

project.tasks.withType<MyBaseTaskType>().configureEach {
  myCommonData.convention( ... )
}

I have for example many tasks which are run only sometimes and I doesn't need to cache their result.

You could also make them as incompatible with CC, then CC is not used if they are to be executed, but that's by far not the preferable solution

I basically don't need

@get:Nested 
  abstract val myCommonData: Property<MyCommonData>

But to have Properties inside of MyCommonData like class MyCommonData { val version : Property<String> val versionCode : Property<Int> val commitHash : Property<String> } And here I don't know how to create a instance of Property

Just let Gradle instantiate it

And it will be also automatically serializable?

Should be, yes, especially when it is a managed type

check out the docs here for using

objects.newInstance()

https://docs.gradle.org/current/userguide/custom_gradle_types.html#nested_objects and here for getting an instance of ObjectFactory (because config-cache forbids using

Project.getObjects()

!) as well as other services

At configuration time it should be ok to use it, shouldn't it?

At configuration time it should be ok to use it, shouldn’t it?

🤷‍♀️ config-cache is always a mystery to me. One thing works, another spits out an indecipherable error. I just always inject and use build services, and never use

Project

Yes. I think that access project is prohibited only in exec method.

yep

I want to basically let's task to fill all inputs itself. I will do something like this

project.tasks.register<RemoteSignApkTask>("${variant.name}ApkRemoteSign") {
    setup(variant, gitClient, somethingElse)
}

And task will collect data that needs from theese objects. Create this POJO class instance and fill @Input field with it. I don't want to repeat setup of all inputs everytime I'm using it. And change it on several place when input requirement will change.

If you talk about Groovy DSL, that is not Gradle, but just plain Groovy: jdoodle.com/ia/Hml

No. I'm not using Groovy, just Kotlin. I had Kotlin task with method setup() and Gradle handled it as property during the automatic class enhancement.

Well, probably adapted to how Groovy handles it 😄