This message was deleted.

Hey, @Jakub Chrzanowski! I think what you have or some variation of it makes sense. 1. Cacheable

createFooFile

2. Non-cacheable

printFooFile

that depends on

createFooFile

Is the following still a valid way for making task non-cacheable?

outputs.upToDateWhen { false }

So, that will disable incremental building (up-to-date checks) for the task which is different from build caching. You may want to read the docs on incremental building vs build caching.

And otherwise, it would be

@UntrackedTask

or

doNotTrackState()

🙂 Btw. your question should probably have gone to #CA83B1VLL, as it has nothing to do with configuration cache. 😉

Oh my, it should go to #CA83B1VLL indeed, my bad!

@UntrackedTask

is a newer annotation but I believe that is a valid use case. See the JavaDoc.

Since 7.3 - so I still have to wait a bit. We're supporting 7.1+ now

Do you have inputs and outputs for

runIde

task? If you have neither,

@UntrackedTask

will just be a noop, as there is nothing to track anyway.

It takes inputs, but produces nothing.

Yeah, then I'd add the annotation once you are on recent enough version, or do the runtime-api call depending on the current Gradle version, so that the inputs do not even need to be fingerprinted. But for always rerunning not having any output defined would already be sufficient.